While MapEntry is displayed as a vector it isn't actually a collection
(which is a mistake I sometimes make also), so empty behaves as expected.
On Friday, 18 July 2014 10:45:19 UTC+1, Brian Craft wrote:
>
> => (empty [:foo 5])
> []
> => (first (mapv identity {:foo 5}))
> [:foo 5]
> => (empty (first (mapv identity {:foo 5})))
> nil
>
> What just happened there? Is this expected? In the second and third cases
> the type of the vector is clojure.lang.MapEntry, which I expect is the root
> of the behavior, but this seems very inconsistent. Is there a way to get
> the behavior one would expect? Should clojure.core/empty be avoided?
>
--
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.
