Tai Chi Minh Ralph Eastwood

@mewalig What is your progress on this? I am currently working on this as well. I did an experimental cygwin build but ran into issues with `fork`s not supporting access...

Yeah supporting `proc` is pretty much impossible for networking purposes on Windows. I think the stack magic should be fine if the coroutines are confined per thread and the user...

> To be frank, the construct doesn't work that well on UNIX either. If you proc() later on in the parent's life cycle all the junk allocated by the parent...

While preparing the code-base for thread support I accidentally found some flags to make context switching an order of magnitude faster if you compile statically. It gives a tiny speed-up...

The generated assembly seems to show inlines everywhere and reduced it to simply context switching from main thread to the worker. It does do the scheduling as well but removes...

Interestingly libdill works perfectly fine on Ubuntu for Windows! Shame it's still in beta.

Due to significant differences with the windows I/O system and unix polling mechanisms it's not easy to port - your best bet is to use Ubuntu for Windows but of...

That's true - I just want to keep note in case we need to use it for Windows - the patch in #18 uses it.

I stepped back a little bit and did some quick reading on CSP (sadly I'm not so much of an expert in this area despite being in an office with...

Answering your third point above: I agree with those thoughts. Having multiple `chrecv` on the same channel from multiple `go` effectively covers the non-deterministic use case. In some ways, this...