Add wasm-opt-for-rust-m1.md

[brson]

Milestone Delivery Checklist

• The milestone-delivery-template.md has been copied and updated.
• The invoice form 📝 has been filled out for this milestone.
• This pull request is being made by the same account as the accepted application.
• In case of acceptance, the payment will be transferred to the BTC/ETH payment address provided in the application.
• The delivery is according to the Guidelines for Milestone Deliverables.

Link to the application pull request: w3f/Grants-Program#1070

[brson]

cc @cmichi @Robbepop @kripken wasm-opt-for-rust milestone 1

[brson]

Note that if somebody actually tries to install the binary for this "preview" version, they will need to specify the version explicitly, like cargo install wasm-opt --version 0.0.1-preview.3 --locked, as cargo will not select prerelease versions by default.

[lucasvanmol]

Thank you for the excellent delivery @brson! I’ve accepted it, evaluation here.

Regarding this comment in the delivery document:

As of now we believe that wasm-opt's fuzzing capabilities are not important for our use cases, and intend to not include them in the API. Feedback welcome.

That’s totally fine. If you wish you can submit an amendment to your application so that we are aware of this for the next milestone evaluation.

Finally, I'll notify the finances team to pay out your invoice; please allow for up to two weeks for processing.

[github-actions]

Congratulations on completing the first milestone of this grant! As part of the Grants Program, we want to help grant recipients acknowledge their grants publicly. To that end, we’ve created a badge for projects that successfully deliver their first milestone. Note that it must only be used within the context of the delivered work, so please do not display it on your team or project's homepage unless accompanied by a short description of the grant.

Furthermore, you're now welcome to announce the grant publicly. Please remember to observe the foundation’s guidelines in doing so. In case you haven't done so yet, you may also reach out to [email protected] for feedback on your announcement and cross-promotion.

Thank you for your contribution and good luck with the remaining milestones, if any! As usual, please let us know if you run into any delays by leaving a comment on the application PR, or directly submitting an amendment.

[brson]

Thanks for the evaluation @lucasvanmol and for running tarpaulin on it. I filed an issue (brson/wasm-opt-rs#59) to look into it. It's not surprising that a tool that exercises the program in new ways would find a segfault - particularly in the low level bindings there are code paths that binaryen doesn't expect and will fail hard. I'll figure out how to get taurpaulin working, and consider running at least the high-level apis through additional analysis tools to see if they uncover any more obvious segfaults.

[lucasvanmol]

I'll figure out how to get taurpaulin working, and consider running at least the high-level apis through additional analysis tools to see if they uncover any more obvious segfaults.

Thanks for that! I mentioned it because I thought it might be of interest to the project, but note that it's not a requirement for us in terms of milestone delivery - you're of course free to look into it on your own volition.

[cmichi]

It's great to see this going well, looking forward to M2 😊!

Non-ascii paths on Windows don't work.

Nice to see that you are thinking about issues like this.

[RouvenP]

hi @brson we transferred the payment today.

[brson]

@RouvenP I have received the payment. Thank you.