Thomas Lively

I've been assuming we would eventually do the escape analysis to figure out what types we can safely modify, but I agree that lots of types will probably escape. A...

Current dependencies on/for this PR: * main * **PR #4843** 👈 * **PR #4844** This comment was auto-generated by [Graphite](https://app.graphite.dev/github/pr/WebAssembly/binaryen/4843?utm_source=stack-comment).

@askeska-google has requested that we merge this after merging a solution for https://github.com/WebAssembly/binaryen/issues/4824.

:tada: It would be great to fix this in check.py as well.

Yeah, now that the SIMD proposal is finished, it would be good to document this. For now, you can look at src/js/binaryen.js-post.js to see what is available. FWIW (and this...

Some TODOs along this vein: - [ ] Store function parameter types separately rather than all together as a tuple - [ ] Investigate the performance impact of having `Type`...

This is an interesting idea! > The rationale I have for this is that when compiling Rust, even with the bulk-memory target feature (codegen option) enabled, a lot of naive...

The Rust-emscripten regression mentioned in the opening post is fixed in https://github.com/rust-lang/rust/pull/67976, which has been approved but might take a while to get through the commit queue. Please cc me...

I would prefer not to validate - it gives optimizations more flexibility and less to think about and does not have a significant performance cost. For the fixup pass, I...

> not actually validating 1a on our output In debug mode perhaps we can add some extra validation as part of module writing. > intermediate states do not validate on...