I'm also wondering if there is any advantage at all to using key/val over first/second. The only downside I can see is that the code won't be clear.
On Wednesday, 4 May 2016 09:52:40 UTC-7, adrian...@mail.yu.edu wrote: > > I may be misremembering here, but I think this was briefly implemented for > an alpha release of 1.8.0. I think the entire feature in question is being > reworked for the future, but I'm uncertain of the details. Perhaps others > can chime in with the background motivating those changes and reversions? > > On Wednesday, May 4, 2016 at 12:44:19 PM UTC-4, JvJ wrote: >> >> >> I've noticed that, in Clojure, there is a MapEntry type that supports the >> operations "key" and "val", but in Clojurescript, MapEntry is replaced by >> simple 2-element vectors. >> >> Furthermore, 2-element vectors can be used in almost all other cases >> where a MapEntry is expected, and MapEntries support all vector >> operations,but "key" and "val" are >> not supported on these vectors. >> >> Is there a particular design reason for this? It doesn't seem like much >> more than an inconvenience >> > -- 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.
