It's a real problem for me too, I also wonder what was the intention behind this. I guess there could be a very good reason for this special treatement of nils, but I haven't seen it yet.
I would love to hear about this from people involved in core.async development. On Friday, August 16, 2013 4:44:48 AM UTC+2, Mikera wrote: > > Hi all, > > I'm experimenting with core.async. Most of it is exceptionally good, but > bit I'm finding it *very* inconvenient that nil can't be sent over > channels. In particular, you can't pipe arbitrary Clojure sequences through > channels (since sequences can contain nils). > > I see this as a pretty big design flaw given the ubiquity of sequences in > Clojure code - it appears to imply that you can't easily compose channels > with generic sequence-handling code without some pretty ugly special-case > handling. > > Am I missing something? Is this a real problem for others too? > > If it is a design flaw, can it be fixed before the API gets locked down? > -- -- 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/groups/opt_out.
