Amendment: no fuzzing in wasm-opt-for-rust #1195
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.
Project Abstract
This is a minor amendment to the
wasm-opt-for-rust
grant, which explicitly states that fuzz-testing capabilities are out of scope. The subject was not mentioned in the original application.Fuzz testing of output is a feature of the underlying tool. It is not used by any known prospective clients, and is probably mostly useful to the the Binaryen project themselves for verifying that the optimizer works correctly.
As discussed in the M1 review.
Functionally this project is all but complete. Integration with
cargo-contract
and Substratewasm-builder
has begun. The biggest task remaining is to publish a blog post.#1070