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

status bug when start a parent coroutine when should yield child #4

Closed
owent opened this issue Jan 3, 2017 · 1 comment
Closed
Assignees
Labels

Comments

@owent
Copy link
Owner

owent commented Jan 3, 2017

If there are coroutine A and B.

Run ROOT->A.start()->B.start()->A.start()

Yes, it should be B.yield() when we want to switch back to A.But A.start will success and some data will have problem.(caller and other datas)

@owent owent added the bug label Jan 3, 2017
@owent owent self-assigned this Jan 3, 2017
owent pushed a commit that referenced this issue Jan 3, 2017
@owent
Copy link
Owner Author

owent commented Jan 3, 2017

fixed

@owent owent closed this as completed Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant