On Nov 10, 7:07 am, David Brown <cloj...@davidb.org> wrote: > Ok. So, it's the existence of this future-like entity that blocks > upon deref until filled is indeed somewhat missing. It's not > particularly difficult to implement. > > This thing could easily create a lazy sequence, in fact, the code > would look a lot like the code for seque, with just a separation of > the writer from the reader. I'll have to think about it to make sure > that it can be used safely.
You might want to look at the (recently added) fill-queue (in clojure.contrib.seq-utils), which provides a lazy seq that is filled by another thread and blocks if readers consume faster than the queue is filled; maybe your problem fits into this mechanism. -- 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
