-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Does libaco only have the implementation of shared stack mode? #19
Comments
libaco also support standalone-stack coroutine. As the documentation described, if a shared stack has only one user coroutine, then we could call this coroutine a standalone-stack coroutine. There is also a demonstration of a standalone-stack coroutine in the test_aco_tutorial_2.c. I hope this answer is helpful for you :D |
Yes I see. Thank you! |
Since the But as a hack with older gcc (before gcc4.6), you could try the build command below (since all the _Static_assert check during compiling time in libaco is always true on nearly all common platforms): $ EXTRA_CFLAGS='-D_Static_assert(...)=' bash make.sh |
Thank you very much for your report, @lancewz ;-) I would like to add such friendly support for older gcc in the next release of libaco. |
I build libaco successfully follow your advice. |
It is a very cool and nice idea :D I'm now developing a golang-like & libaco-based C coroutine scheduler and would probably be released in several days. These two projects we are developing have something in common. Looking forward to your excellent project! |
只有共享栈的实现么?
Does libaco only have the implementation of shared stack mode?
The text was updated successfully, but these errors were encountered: