-
Notifications
You must be signed in to change notification settings - Fork 339
Async successors #363
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
Async successors #363
Conversation
I think the error is saying you're calling We should store the future returned by |
Anything I’d we would need to do to get this merged? 🤩 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great; thanks heaps!
Created a backup of the async impl here for future reference (e.g. when we get async closures): https://gist.github.com/yoshuawuyts/32fb44959c0bd66a683008ee1d540500. Thanks! |
This doesn't compile at the moment, but I felt it was easier to get pointers on code than hypotheticals in Discord.
The current compile error is:
which confuses me because I thought I had that trait bound on the
where
?