That's what I came up with. alts is very powerfull ! thanks
On Friday, September 12, 2014 11:56:56 PM UTC+2, Dylan Butman wrote:
>
> How about this?
>
> https://gist.github.com/pleasetrythisathome/4f03ba9f729300beea40
>
> On Friday, September 12, 2014 12:51:39 PM UTC-4, Jeremy Vuillermet wrote:
>>
How about this?
https://gist.github.com/pleasetrythisathome/4f03ba9f729300beea40
On Friday, September 12, 2014 12:51:39 PM UTC-4, Jeremy Vuillermet wrote:
>
> thx, I'll look more into in but it doesn't seem they are able to pause and
> resume scheduled functions
>
> On Thursday, September 11, 20
thx, I'll look more into in but it doesn't seem they are able to pause and
resume scheduled functions
On Thursday, September 11, 2014 4:34:16 PM UTC+2, Linus Ericsson wrote:
>
> For instance you can use schejulure [1] or at-at [2] and make sure the
> scheduled function calls put an item (event)
Yes when I write block I meant park.
My first idea was to use a control channel which have pause and resume
input but then my question is
> You should never block a go loop other than by using a parking channel op
> (like !, etc).
>
> You probably instead want a control channel where you can se
You should never block a go loop other than by using a parking channel op
(like !, etc).
You probably instead want a control channel where you can send it a pause
message telling it to block on the control channel until a resume message
arrives.
On Thursday, September 11, 2014 6:52:48 AM UTC-5
For instance you can use schejulure [1] or at-at [2] and make sure the
scheduled function calls put an item (event) on the channel and then made
the scheduler do the pausing work.
All the "listeners" attached to the channel will receive the events at the
time the scheduler "releases" them, and you
