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

bug: Use of unstable Rust feature: async move in a closure #361

Closed
eureka-cpu opened this issue Jun 5, 2023 · 0 comments · Fixed by #365
Closed

bug: Use of unstable Rust feature: async move in a closure #361

eureka-cpu opened this issue Jun 5, 2023 · 0 comments · Fixed by #365
Labels
bug Something isn't working

Comments

@eureka-cpu
Copy link
Contributor

eureka-cpu commented Jun 5, 2023

Looking at what seems to be an attempted use of an async move closure which is still unstable: https://github.com/vrrb-io/vrrb/blob/main/crates/node/src/runtime/mod.rs#L305

The closure is trying make a new thread take ownership of the output of an async function. If await isn’t called the thread effectively takes ownership of nothing since the Future is never used. If you await it however, you end up with the above which is being tracked in rust-lang/rust#62290 and still unstable in Rust.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant