Skip to content
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

Request: having a version of aco_yield() that receives the coroutine to where to yield #31

Open
AltraMayor opened this issue Oct 23, 2019 · 0 comments · May be fixed by #32
Open

Request: having a version of aco_yield() that receives the coroutine to where to yield #31

AltraMayor opened this issue Oct 23, 2019 · 0 comments · May be fixed by #32

Comments

@AltraMayor
Copy link

In the case I'm considering using libaco, I'll have less than 20 standalone non-main coroutines and the cost to switch between the coroutines is critical. The current cost of 10ns for acosw() fits my application, but having to go through the main coroutine first to switch to another non-main coroutine puts the cost of switching at 20ns, what becomes too much for what I'm trying to accomplish.

Is it possible to have a version of aco_yield() that receives the coroutine to where to yield?

@AltraMayor AltraMayor linked a pull request Oct 24, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant