My interpretation is that the hash code issue (if correct) is an implementation detail, and that this should indeed be considered a bug because nil certainly seems like a compile-time literal to me. It's also an especially useful value in the context of something like case. In any case, thanks for your response.
On Aug 30, 5:12 pm, Stuart Sierra <the.stuart.sie...@gmail.com> wrote: > "case" does constant-time dispatch using the hash codes of the test > values. Since nil is Java null, it doesn't have a hash code, so > "case" can't handle it. > > I wouldn't call it a bug, but there is work to be done on extending > "case" to edge cases like this. -- 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
