Lingming Zhang

> > suppose there is a wasm module containing only data segments > > Data segments are not valid without a memory, though? Every data segment refers to a memory....

> I see, thanks. Yes, it sounds like we should find a way in the C API to support such modules. @kripken Actually, Binaryen does support parsing modules which contain...

@kripken hey kripken, I added corresponding API in PR #6346, you can check that out :).

The `CI / build (windows-latest) (pull_request)` failed at test stage, and it seems like the built `wasm-as.exe` could not even print the version info. Thus, I tried to manually reproduce...

Hey Kripken, I made corresponding code changes according to your comment. For the CI issue, I finally found out it's still related to the static initialization problem and fixed it...

Hey @kripken, sorry to bother but any further suggestions?

> Atm Binaryen is optimized for short-running processes, like calling `wasm-opt` from the commandline to optimize a module. After the optimization the process ends, which is how toolchains (Emscripten, J2CL,...

> We similarly intern types and never delete them, but we do have a function called `destroyAllTypesForTestingPurposesOnly` that deletes all the interned types. It's wildly unsafe to use, but I...

> > > We similarly intern types and never delete them, but we do have a function called `destroyAllTypesForTestingPurposesOnly` that deletes all the interned types. It's wildly unsafe to use,...

> How about to use arena or bump allocator for interner? I guess generated names could be quite long and continuously grow in "converge" mode, which may caused to OOM...