> The real use case of M:N would be IMHO to make NimGo handles millions of I/O > at the same time, without the help of threads, it is just not possible, the > I/O loop is not free.
It is not for performance (though it hopefully is an **enabler** for performance) but for convenience. > But I think that "particular" case would be better handle by another library > than NimGo. So let's build it on top of NimGo. My point of view is quite simple and naive: Having "solved" the parallelism story with Malebolgia (though maybe we need to reintroduce FlowVars...) I'm left with these blocking read/write calls. I see your NimGo library as a solution.
