Thanks for your response, it is important to know. (Sorry for my lexical 
typo: *unbound**ed*. I didn't realize it derives from the verb *bound*, not 
*bind*!)

My question on channel boundaries still holds though. Why the enforcement 
of boundaries *always*?

On Wednesday, July 3, 2019 at 5:16:31 PM UTC+2, Ghadi Shayban wrote:
>
> (chan) is not a channel with an unbounded buffer. It is a channel with 
> *no* buffer and needs to rendezvous putters and takers 1-to-1.  
> (Additionally it will throw an exception if more than 1024 takers or 
> putters are enqueued waiting)
>
> On Wednesday, July 3, 2019 at 7:14:46 AM UTC-4, Ernesto Garcia wrote:
>>
>> You can create a unbound channel with (chan), but not if you use a 
>> transducer; (chan nil (filter odd?)) will raise an error that no buffer 
>> is provided. Why is this the case?
>>
>> Why the enforcement of all channels to be bound? In a program, there will 
>> be channels that propagate to other channels, so only channels at the 
>> boundaries would require to be bound?
>>
>> Channel limits are also much dependent on the particular process and 
>> environment. How would we write generic code that creates channels, if 
>> those need to be bound to limits unknown?
>>
>> Thanks,
>> Ernesto
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/7f9f5efe-883f-47e4-b2a5-a457fb7444ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to