Another <chasm release>, and theres a bunch of int...

# webassembly

[Charlie Tapping]

Another chasm release, and theres a bunch of internal changes so if you’re using chasm I would suggest updating.

TLDR

• Chasm now uses wasm-tools rather than wabt internally for its automation of the official wasm testsuite. wabt is largely unmaintained and lacked support for modern proposals so was preventing me automating tests of the gc proposal. Previously I’d hand implemented these gc tests... This update changes that, we now have 100% automation and coverage of all proposals supported. For this reason I happy to say chasm is production ready… but bare in mind it lacks a stable abi until we 1.0.
• I’ve added a module information api, this api is designed to support codegen, it describes modules in terms of their imports and exports alongside providing all the necessary type information you would need to say … generate kotlin classes.
• Theres an api for creating tags but thats not all that interesting unless you’re building debug tooling
Next steps

• Threads proposal, this is the last proposal ahead of the 1.0. I’d expect to see this in the next month…ish
• Final changes to the api with some contingency for enabling the forthcoming proposals (component model etc)
• Repo hygiene, automation of publications, benchmarks, codecov etc
• Documentation, I’d like others to be able to contribute to the repo but I appreciate it’s not your average project and this might seem challenging. I’m going to add some high level documentation to the repository, detailing the how, what , why and a getting started for adding support for new proposals.

[Frank Bouwens]

Nice! 🎉

[darkmoon_uk]

This looks like an amazing technical achievement; well done!
What are some use cases you envision?