It is the expected behavior for everyone who has ever gotten burned by this bug :)
Seriously though, this has come up several times over the last couple of years. I remain baffled that this has never been fixed (at least not as of 1.3). There are two ways this could potentially be fixed. On the one hand, transients could be made to implement more of the interfaces they are expected to implement. On the other hand, contains? could be modified to return a meaningful error rather than false when passed something that doesn't support that interface. Or better yet, both of these fixes would be a good thing. -- 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
