Why would you want this? To leave the value inside the channel for other consumers?
In that case there would be no guarantee that the value returned by the peek operation is the next value in the channel, because it might have been consumed already. Best regards, Leon On Monday, September 29, 2014 12:12:33 PM UTC+2, Nahuel Greco wrote: > > Currently if you block/park on a channel reading it by using <!!/<! or > alts!/alts!! the value will be consumed when it appears, so there is no way > to block/park waiting a new value without removing it from the channel. > There is a non-consuming peek operation planned in the core.async roadmap > or a design rationale exists for not including that operation? > > Saludos, > Nahuel Greco. > -- 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 unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
