Sets when used as functions are not predicates the do not return true or
false based on membership.
They return the looked up value, in this case false. You can say "well I
passed in the value, why would I want it back" but sets don't need to
return an identical object, just an equal object (could have different
metadata etc.
This behavior is not a bug. It seems unlikely that this interface/contract
would be changed, do you have compelling case for change?
On Jan 21, 2012 7:46 PM, "Mark Engelberg" <mark.engelb...@gmail.com> wrote:
> I believe it is a bug that:
> (#{true false} false) yields false
> whereas
> (contains? #{true false} false) yields true
>
> Can someone confirm or deny 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
--
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
