You are not alone - it's the number one frustration in the community https://www.reddit.com/r/Clojure/comments/433y02/state_of_clojure_2015_survey_results/
But also see the responses - maybe we will have some major improvements with 1.9. Spec looks like good infra to support those efforts for improving macro errors. On a practical note - and it's not a 'solution' - iterative development can helps since you can go usually go back to a known good position and work backwards. Like I say, not a great solution but might help to reduce the frustration. Ray On Friday, 22 July 2016 18:10:21 UTC+2, Peter Romfeld wrote: > > NPE is just so painful! most exceptions are not that easy to debug, would > be cool if it could say from where the problem was initiated.. (well > because most of the time i forget to print the stacktrace with > `print-stack-trace `) > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
