On Jan 18, 5:17 am, Mark Engelberg <mark.engelb...@gmail.com> wrote:
> On Fri, Jan 9, 2009 at 6:00 AM, Rich Hickey <richhic...@gmail.com> wrote:
> > When I hadlazy-seqin play, many of those were defined that way. The
> > real cost is explaining either whylazy-seqis private, or, if public,
> > when/how to use it.
>
> I'd certainly make use oflazy-seqif it were public. But assuming
> it's not made public, are you thinking right now that the underlying
> clojure.lang.LazySeq will eventually go away, or can power users use
> it and count on it being there, although not explicitly exposed
> through the api?
I want to hold off on that decision until I get streams out, and I
think you should too :)
Rich
--~--~---------~--~----~------------~-------~--~----~
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
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
-~----------~----~----~----~------~----~------~--~---