On Fri, Jul 8, 2011 at 1:00 AM, Ken Wesson <kwess...@gmail.com> wrote:
> > On Thu, Jul 7, 2011 at 11:21 PM, Ken Wesson <kwess...@gmail.com> wrote: > >> ... it won't use the protocol to cache the result. Making it do so, > however, > >> would cause problems if one had (seqable? some-foo) and later attempted > >> to extend the protocol to mark Foos as seqable within the same runtime > >> session. > Problem for who? Problem how? Extending seqable? to types you do not control or which are not seqable? as defined by Clojure itself is asking for trouble anyhow. David -- 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
