Re:Five Things that Mildly Annoy Me in Clojure
by amix on Wednesday June 17, 2009 @05:01PM
(#662474)
It's Java's stack trace alright, but the stack traces are not that useful since they mostly relate to tons of internal Clojure related stuff - - than the written code.
Like the blog author notes: "Stack traces in Clojure will often tell you little to nothing about what is causing the error, or more importantly, where it's coming from in your code." - - The most important property of a stack trace is to tell you where the bug is coming from in your own code - - and this is a non trivial task if you compile down to a low-level language.
Like the blog author notes: "Stack traces in Clojure will often tell you little to nothing about what is causing the error, or more importantly, where it's coming from in your code." - - The most important property of a stack trace is to tell you where the bug is coming from in your own code - - and this is a non trivial task if you compile down to a low-level language.