Martin Sustrik
Martin Sustrik
I suggest you rather send a GitHub pull request. It'll make easier for people to look at the patch and test it. I, personally, don't own a Win box, so...
Have you considered simply not supporting proc on Windows? To be frank, the construct doesn't work that well on UNIX either. If you proc() later on in the parent's life...
As for thread(), yes, that would work better than proc(), but then, isn't that just asking for problems when libdill's stack magic clashes with pthreads' stack magic?
Interesting, one would say that 6ns wasn't even possible. Maybe it's because of additional inlining that can be done when linking statically?
One thing to check (a project that builds epoll on top of IOCP): https://github.com/piscisaureus/wepoll
There used to be an equivalent of go() that forked a new process, e.g. proc(fn(1, 2, 3)); However, it's not clear what the semantics of such function should be. The...
I am not against providing some kind of forking API, I am just genuinely not sure what the semantics should be. Maybe just killing all the threads but the running...
Ok, sounds reasonable. I'll try to dig out the old code and hack something together.
There are 3 scenarios: 1. Forceful shutwdown (hclose). Shuts down immediately, no guarantees about sending anything (even RST) to the peer. 2. Orderly shutdow (tcp_close). Sends FIN to peer, then...