We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
shouldn't we close the scope in AsyncAfter since we also opened one?
The text was updated successfully, but these errors were encountered:
scope.Close(Undefined());
Sorry, something went wrong.
I assume you mean return scope.Close(Undefined());
I don't think you need to call scope.Close() unless you want to 'rescue' a handle from destruction from the HandleScope.
In this case, I don't see why you would need to rescue the Undefined handle, it should just be
return Undefined();
// and let scope to clean up whatever handles it likes the undefined handle won't be cleaned up like other handles, as far as I know.... right?
No branches or pull requests
shouldn't we close the scope in AsyncAfter since we also opened one?
The text was updated successfully, but these errors were encountered: