Neco

I love how simple and elegant is this to use: https://github.com/tidwall/neco/blob/main/examples/echo-server.c I was going to actually implement an echo server for load balancer…

yeah i like this model. then you can use whatever synchronization junk you prefer to share state between the threads, if you have any. your library looks well written and clean.…

This library aims to be the simplest and most efficient thing for what it does. And what it does is perfect for is managing communications with things that themselves may be…

the scheduler is probably simpler if coroutines can't bounce between cores. you can have a single thread per core that runs the scheduler to multiplex a bunch of coroutines on…

Coroutines are still very useful for multitasking even if you're not sharing tasks between CPU cores. Other coroutines can just execute whenever something would normally block,…

This library aims to be the simplest and most efficient thing for what it does. And what it does is perfect for is managing communications with things that themselves may be…

Can someone help elucidate why "It's a non-goal for Neco to provide a scalable multithreaded runtime, where the coroutine scheduler is shared among multiple cpu cores [...]" this…

Goroutines aren't coroutines. This isn't a nitpick, it's pretty essential to understanding the goals and non-goals of Neco. Coroutines are a control-flow primitive which allows…

I think the replies l got here more or less proves my point. So a coroutine is basically something you can explicitly yield control flow from or give control flow to. neco…

These are coroutines. Just... look at the code, this isn't a proprietary binary product where you have to take someone's word for it. They're very clearly coroutines. I don't…

These are cooperatively scheduled green threads... I feel the word "coroutine" is slowly losing its original meaning, similar to what happened to "lambda".

In "Example 4", I don't understand where the "arg2" in `free(arg2)` is coming from?

How does it work on WebAssembly, where there's no native support for stack switching? Does it rely on Emscripten's Asyncify transformation?

Yes according to the caveats section in the llco subproject: > Webassembly: Must be compiled with Emscripten using the -sASYNCIFY flag.

Can someone explain how this works please? How does it prevent this from saturating the CPU? ``` while (1) { neco_sleep(NECO_SECOND*2); printf("tock\n"); } ```

I encourage you to dig through the source. There's not that much. Either this is a library you might use, so you should obviously review the code before you include it in your…

I’ve used libaco with a lot of success in the past (mixing uv, curl, and zlib in a way that made the zlib loop easier to manage (since it looked like a normal read, decompress…

yeah i like this model. then you can use whatever synchronization junk you prefer to share state between the threads, if you have any. your library looks well written and clean.…

yeah i like this model. then you can use whatever synchronization junk you prefer to share state between the threads, if you have any. your library looks well written and clean.…

It's a little lower level than what you have, but you may find somethings interesting here: https://github.com/Keith-Cancel/Bunki