GC and Exceptions in Wasmtime

📝 Discussion Summary (Click to expand)

Key Themes

Missing effects in WebAssembly

"It seems like a bit of a shame that wasm got support for exceptions but doesn't support effects which are a generalisation of the same concept." — faldor20
Technical barrier: stack unwinding vs. switching

"I'm guessing this may be because exceptions exclusively require stack unwinding where as effects require full stack switching." — faldor20
Hope for future stack‑switching support

"Seems like there is still progress on that though which gives hope." — faldor20

🚀 Project Ideas

Generating project ideas…

A lightweight WebAssembly runtime that adds effect handlers (e.g., exceptions, async continuations) to existing Wasm modules without manual stack manipulation.
Enables developers to write effectful code using familiar control‑flow constructs.

Key	Value
Target Audience	WebAssembly developers, language compilers, toolchain maintainers
Core Feature	Integrated effect‑handler API and compiler extensions for stacking operations
Tech Stack	Rust (wasm‑bindgen), AssemblyScript, WASI, Emscripten
Difficulty	Medium
Monetization	Revenue-ready: SaaS licensing (tiered subscription)

Directly addresses HN commenters' frustration that Wasm supports exceptions but not generalized effects.
Provides practical utility for building language runtimes (e.g., Lua, Python) that target Wasm with rich control flow.

A browser‑based visual debugger that animates stack‑switching and exception unwinding in WebAssembly, helping developers understand and debug complex control‑flow scenarios.
Turns abstract stack‑switching proposals into interactive diagrams.

Key	Value
Target Audience	WebAssembly engineers, researchers, debugging tool developers
Core Feature	Real‑time visualization of stack frames, switch points, and exception propagation
Tech Stack	TypeScript, React, WebGL, WebAssembly System Interface (WASI)
Difficulty	Low
Monetization	Hobby

Highlights the gap noted in the HN discussion about “exclusively require stack unwinding where as effects require full stack switching.”
Generates discussion by showcasing a tangible tool for a currently speculative proposal.

A cloud service that lets developers write effectful functions in high‑level languages and compile them to Wasm modules with automatic effect handling, reducing boilerplate.
Offers a marketplace for reusable effect handlers (e.g., logging, transaction, async).

Key	Value
Target Audience	Backend engineers, language designers, SaaS developers
Core Feature	Web UI for writing effect specifications, backend compiler to Wasm, CDN distribution
Tech Stack	Go (microservices), Python (frontend), Docker
Difficulty	High
Monetization	Revenue-ready: pay-per-invocation pricing

Solves the pain point of “generalisation of the same concept” that HN commenters feel is missing.
Sparks conversation about tooling for next‑generation Wasm effect systems while offering commercial potential.