Add wasm-opt-for-rust-maintenance-6 #875
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#1305
Again smooth sailing, not a lot of maintenance required.
We have begun work on the upgrade to Binaryen 113.
We discussed with the binaryen authors the APIs needed to support in-memory module optimization, and I think we are in agreement about what needs to be done there.
Sadly, Soroban is disabling wasm-opt by default in their tooling - the C++ build is an obstacle for their users because sometimes the local toolchain doesn't work, and because it takes a long time to build. I think this is evidence supporting a rewrite of wasm-opt in pure Rust - the C++ build component is the weak link in this project.