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
Asynchronous functions are unsound in the presence of the garbage collector #1338
Comments
Xaeroxe
added a commit
to Xaeroxe/napi-rs
that referenced
this issue
Oct 7, 2022
Xaeroxe
added a commit
to Xaeroxe/napi-rs
that referenced
this issue
Oct 7, 2022
Xaeroxe
added a commit
to Xaeroxe/napi-rs
that referenced
this issue
Oct 7, 2022
Xaeroxe
added a commit
to Xaeroxe/napi-rs
that referenced
this issue
Oct 9, 2022
Xaeroxe
added a commit
to Xaeroxe/napi-rs
that referenced
this issue
Oct 9, 2022
Brooooooklyn
pushed a commit
to Xaeroxe/napi-rs
that referenced
this issue
Nov 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual Output
Expected
I expected the call to
runForever
to keep a reference to theawesome
instance alive until the function finished execution.Steps to reproduce
lib.rs
Cargo.toml
run.js
package.json
Running
yarn run x
.The text was updated successfully, but these errors were encountered: