|Number of watchers on Github||971|
|Number of open issues||2|
|Average time to close an issue||2 days|
|Average time to merge a PR||about 4 hours|
|Open pull requests||0+|
|Closed pull requests||1+|
|Last commit||about 4 years ago|
|Repo Created||about 8 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||cloudwu|
|Do you use coroutine? Leave a review!|
|View open issues (2)|
|View coroutine activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
It's an asymmetric coroutine library (like lua).
You can use coroutine_open to open a schedule first, and then create coroutine in that schedule.
You should call coroutine_resume in the thread that you call coroutine_open, and you can't call it in a coroutine in the same schedule.
Coroutines in the same schedule share the stack , so you can create many coroutines without worry about memory.
But switching context will copy the stack the coroutine used.
Read source for detail.
Chinese blog : http://blog.codingnow.com/2012/07/c_coroutine.html