-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
newest asyncdispatch recursion #6100
Labels
Async
Everything related to Nim's async
Comments
Yes, we discussed this in the PR. You need to initialize the event loop. |
Just to be sure, you don't forget to fix it. |
Also if i understand PR correctly you introduced this bug again, to allow developers use Futures without Dispatcher. Earlier this use-case was prohibited, but with newest PR its possible again. |
yglukhov
added a commit
to yglukhov/Nim
that referenced
this issue
Jul 14, 2017
yglukhov
added a commit
to yglukhov/Nim
that referenced
this issue
Oct 27, 2017
yglukhov
added a commit
to yglukhov/Nim
that referenced
this issue
Dec 1, 2017
Merged
dom96
added a commit
that referenced
this issue
Jan 10, 2018
yglukhov
added a commit
to yglukhov/Nim
that referenced
this issue
Jan 11, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With latest changes to asyncdispatch this small piece of code causes
Stack overflow
.The text was updated successfully, but these errors were encountered: