1.9 could still support the behavior that worked in 1.8 and in CLJS, too, or throw a compile time Exception.
If we had known this change in behavior, fixing it in the codebase wouldn't have been much trouble. But a missing default can lead to errors far away so it takes time to get to the ground of this. If there was no (working) other way to provide a default for namespaced keys in 1.8 I believe that many people will have tried adding the ns and ran with it. On Wednesday, July 6, 2016 at 2:17:14 PM UTC+2, Alex Miller wrote: > > This *is* different than 1.8 (and prior) because it has been buggy since > namespaced keys were added (due to a lack of tests - entirely my fault). > Nothing was ever documented about this behavior - it was purely accidental > and I would consider it in the realm of "unspecified". > > In 1.9 I added additional tests and tightened up this code in the process > of adding the namespaced key support. > -- 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.
