Wow, that Jira item got mired in a muddle of Various Alternatives! It discusses (1) error messages, (2) documentation, and (3) covariant returns! Jira can be a slow place to resolve a muddle.
By the way: I suppose each compiler (clj, cljs, ...) is sensitive to a distinct set of implicitly-reserved method names? What should the documentation explain about portability? Should the list of implicitly-reserved method names be documented? In any case, unless the OP of ticket 1791 cares to reclassify it as a documentation enhancement, someone will need to start a new ticket. Also, if someone has a sturdy theory about better error messages, punch in a second new ticket. The two tickets can be complementary, and proceed at their own pace. -- 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.
