Ah, that's put me on the right track. Thanks Timothy!
-A
On Wed, Jul 17, 2013 at 10:16 AM, Timothy Baldridge wrote:
> After a channel is closed, any gets ( I think some part of your code is taking that nil return value and trying
> to forward it on to a channel. That's what the error is about.
After a channel is closed, any gets ( wrote:
> The problem I am having is in the function at line 41 of
> https://github.com/nodename/async-plgd/blob/master/src/hoare/coroutines.clj.
> Any insight into this is appreciated.
>
> -A
>
>
>
> On Wed, Jul 17, 2013 at 7:23 AM, Timothy Baldridge
> wrote:
The problem I am having is in the function at line 41 of
https://github.com/nodename/async-plgd/blob/master/src/hoare/coroutines.clj.
Any insight into this is appreciated.
-A
On Wed, Jul 17, 2013 at 7:23 AM, Timothy Baldridge wrote:
> True, but I'll mention the semantics of channels once again
True, but I'll mention the semantics of channels once again. Go blocks are
attached to channels, and channels exist on their own as values. No where
in this entire system is there some global list of channels or go blocks
(except for in the executors, but let's not get into that right now).
This m
2013/7/17 Timothy Baldridge :
> It appears that you cannot call close! within a go block and so
>>
>> to signal the end of input to a channel you have to use another channel
>> upon which the receiver can alt!.
>>
>
> That's shouldn't be true. What problems did you run into with this?
Silly sugges
It appears that you cannot call close! within a go block and so
> to signal the end of input to a channel you have to use another channel
> upon which the receiver can alt!.
>
>
That's shouldn't be true. What problems did you run into with this?
And yes, channels and go's are automatically GC'd w
My code is at https://github.com/nodename/async-plgd . Here I reproduce
Hoare's coroutines from the CSP paper, and find that none of the examples
with pipelined coroutines work reliably. I'd appreciate any advice.
On Tue, Jul 16, 2013 at 4:34 PM, Alan Shaw wrote:
> It appears that you cannot ca
It appears that you cannot call close! within a go block and so
to signal the end of input to a channel you have to use another channel
upon which the receiver can alt!.
Some channels that are not stateful, such as a plain copier, would
need no such mechanism. Or would it be good to use such a thi
