Automatic deallocation by `FinalizationRegistry` does not work for fully synchronous code about wasm-bindgen HOT 4 OPEN

Your survey is impressive, thanks so much for such a thorough test.

from wasm-bindgen.

Further literature review suggests that a solution to this problem was attempted by FinalizationRegistry.prototype.cleanupSome proposal.

• https://github.com/tc39/proposal-cleanup-some

However, that proposal was withdrawn on 2023/9.

• tc39/proposals@9b300a2
• https://github.com/tc39/notes/blob/main/meetings/2023-09/september-28.md#withdrawing-finalization-registry-cleanupsome

According to the meeting logs, it seems that it has been decided to attempt to resolve this problem with WebAssembly's JavaScript Promise Integration (JSPI).

• https://github.com/WebAssembly/js-promise-integration

Will this issue be resolved in #3633?

from wasm-bindgen.

Interesting, if the conclusion is correct, which would seem intuitive to me (its called GC after all), it seems to me that there isn't really anything wasm-bindgen can do, right?

Its not clear to me yet if and how the JS Promise integration will be implemented, especially because its just a stopgap for the context switching proposal and isn't even stable yet (and only implemented in Chrome I believe).

from wasm-bindgen.

Thank you for your views. My gut feeling is also that there is nothing wasm-bindgen can do.

Its not clear to me yet if and how the JS Promise integration will be implemented, especially because its just a stopgap for the context switching proposal and isn't even stable yet (and only implemented in Chrome I believe).

Thanks. That answer is good enough for now. I will check after the JSPI is implemented to see what it is and if it can solve this problem.

from wasm-bindgen.