On 6 December 2016 at 01:28, <p...@pwjw.com> wrote: > > And the error messages are not good. > > So I was wondering: Is this a philosophical thing? Or is it an effort > thing? And if it is an effort thing, is there some sort of plan for what > effort to put in? And if so, can I help by closing tickets? >
This is an issue that's been discussed often. The fundamental problem is that in a dynamically typed language, good error messages are often at odds with runtime performance. The more checks we add to catch specific scenarios, or to provide more descriptive scenarios, the more performance tends to be impacted. However, Clojure 1.9.0 may have a solution to that in the form of specs. We can turn on specs selectively at development time, so we get the benefit of detailed error messages, while in production we can turn them off for performance. - James -- 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.
