-
Notifications
You must be signed in to change notification settings - Fork 79
Add 2026 goal for Wasm Components #435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
I like this! As you noted, Rust and WASM were really great back then and I'd love to keep that momentum going. One thing to add: can you please describe the three targets you're introducing in greater detail? Anyone reading this (compiler, libs, lang etc. and myself too at least) should be able to understand: what each target does, what does it bring to the Rust developers and how they differ (why do we need all three)? Doesn't have to go too deep, but a general overview would be really useful. All the teams mentioned will have to approve their part and knowing what it's about and what it will entail will help them make that decision. |
|
@tomassedovic That's a fair point. I've gone ahead and added explainers of each feature in the feature table. |
Co-authored-by: Tshepang Mbambo <hopsi@tuta.io>
Co-authored-by: Tshepang Mbambo <hopsi@tuta.io>
This adds a 2026 goal to improve support for Wasm Components in Rust. Thanks!
cc/ @alexcrichton, @lukewagner
Rendered