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
null pointer for auto free.
May be two 42 in console? I follow one article written by this author, and I find that the result in console still throw null pointer exception.
I found the "the_answer" function has been fixed like this:
const ptr = this.__destroy_into_raw(); const ret = wasm.answer_the_answer(ptr); return ret >>> 0;
but the "__destroy_into_raw" function will work like this:
const ptr = this.__wbg_ptr; this.__wbg_ptr = 0; AnswerFinalization.unregister(this); return ptr;
and the "__wbg_ptr" will be 0 when second-call.
The text was updated successfully, but these errors were encountered:
@alexcrichton may be you can check this problem? Thanks!
Sorry, something went wrong.
Closing in favor of #2168.
No branches or pull requests
Describe the Bug
null pointer for auto free.
Steps to Reproduce
Expected Behavior
May be two 42 in console?
I follow one article written by this author, and I find that the result in console still throw null pointer exception.
Additional Context
I found the "the_answer" function has been fixed like this:
but the "__destroy_into_raw" function will work like this:
and the "__wbg_ptr" will be 0 when second-call.
The text was updated successfully, but these errors were encountered: