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

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. thanks for sharing. if anyone else wants to go coroutine spelunking, these were interesting to me: https://github.com/higan-emu/libco/tree/master https://github.com/higan-emu/libco/tree/master https://github.com/Tencent/libco https://github.com/Tencent/libco https://github.com/hnes/libaco https://github.com/hnes/libaco https://kernel.googlesource.com/pub/scm/virt/kvm/qemu-kvm/+/acd3b6be325a66f8f10f0eed19ed5261ced411cf/coroutine-sigaltstack.c https://kernel.googlesource.com/pub/scm/virt/kvm/qemu-kvm/+/... https://tia.mat.br/posts/2012/09/29/asynchronous_i_o_in_c_with_coroutines.html https://tia.mat.br/posts/2012/09/29/asynchronous_i_o_in_c_wi... https://www.cs.uml.edu/~bill/cs516/context_paper_rse-pmt.pdf https://www.cs.uml.edu/~bill/cs516/context_paper_rse-pmt.pdf