We could definitely implement a different unwinding scheme on the Rust side. Another variation is return-based unwinding, where every call returns an implicit flag indicating the unwinding path. That would not use the js unwind machinery at all. I’ve always wanted such an alternate unwinding scheme anyway, though I can’t remember the other use-cases offhand… certainly it’s useful in places where zero-cost unwinding doesn’t exist (like emscripten).
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Keeping up with WASM developments
|
2 | 1369 | March 25, 2019 | |
Questions about LLVM geneology, Wasm, Emscripten | 16 | 2946 | March 25, 2019 | |
Upgrading Rust’s Emscripten Support | 4 | 2214 | November 11, 2019 | |
WebAssembly roadmap updates (help wanted)
|
3 | 1756 | March 25, 2019 | |
Is anyone working on supporting the newest LLVM version?
|
13 | 5782 | March 25, 2019 |