> It may not have the information on the filename or the line of code like the ordinary stack traces, but these are useless information anyway.
That is the weirdest and most crazy thing I've read in years.
That is the weirdest and most crazy thing I've read in years.
badvalue = dobadthing(); dostuffwith(badvalue);
Depending on the indirection between dobadthing() and the place that chokes on badvalue the stack trace can be completely worthless. It is one of the reasons people hated the original Spring. Claimed it decoupled stuff but all it really did was obfuscate.
I have seen similar claims made about Clojure. Bad data coming from somewhere, but no way to trace it through the system. Sure you can filter bad data in to the garbage can, but that just masks the issue not fix it.
I think the TSTs should also contain the stacktrace. Not or X or Y, but both X and Y.