-
Notifications
You must be signed in to change notification settings - Fork 29
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
Setting the state change waker must take effect for all existing state Var
s too
#220
Comments
anp
changed the title
Setting the state change waker must take effect for all existing state Dec 8, 2020
Runtime::set_state_change_waker
does not set waker for any root function immediately.Var
s too
If I understand correctly from our Discord conversation, the issue you're seeing looks like:
Is that correct? If so this would also be an issue even if you called |
zetanumbers
pushed a commit
to zetanumbers/moxie
that referenced
this issue
Dec 14, 2020
4 tasks
zetanumbers
pushed a commit
to zetanumbers/moxie
that referenced
this issue
Dec 29, 2020
zetanumbers
pushed a commit
to zetanumbers/moxie
that referenced
this issue
Jan 3, 2021
zetanumbers
pushed a commit
to zetanumbers/moxie
that referenced
this issue
Jan 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This needs some change in public API that would also make sense. I think we should require to specify some kind of reference to the waker for each passed function. Should help resolve issue #215.
The text was updated successfully, but these errors were encountered: