dwarf-2-sourcemap VS lang-team

> - A way way better tooling story.

I think this is a real paint point of WebAssembly but it's getting better. You can now compile C/C++ code to WASM using clang as it became a first class citizen in v8 (or later?). Of course, clang does not provide all the runtime goodies that emscripten does but if you limit yourself to use WASM for some part of your code that require performance then all you need to provide is a few Javascript glue code. For prototyping purposes I've bundle an npm package that bring clang to your frontend project without the need to install it through a package [0].

Chrome debugger now support WASM [1] but you still need to install an extension. I've started to work on a way to convert the DWARF symbols from the WASM binary into sourcemap on the fly [2][3] but it still rough around the edge and need some work but it can definitely be done. This would allow WASM debugging natively in any browser supporting sourcemaps.

You also have all the WASM binary tools that you would find for any other kind of executable format in WABT [4].

[0]: https://www.npmjs.com/package/@jdmichaud/wasm-toolkit

[1]: https://developer.chrome.com/blog/wasm-debugging-2020/

[2]: https://github.com/jdmichaud/dwarf-2-sourcemap

[3]: http://site.novidee.com/blog/blog-entry.html?article=2022082...

[4]: https://github.com/WebAssembly/wabt

The Rust team did a deep dive on the bug in 2020, which has some more details that might be helpful to understanding what's going on: https://github.com/rust-lang/lang-team/blob/master/design-me....

I haven't been following this closely, so I looked it up and it looks like that's not going to happen for the foreseeable future unfortunately:

https://github.com/rust-lang/lang-team/issues/122

Kind of a shame, but wrapper types work well enough that I understand. It does look like if there was someone with enough resources to make it happen that they'd be receptive to it.

Did you read the link the original comment posted? I think that explains the idea rather well https://github.com/rust-lang/lang-team/issues/122

A quick search pulled up this as a likely candidate for most recent discussion of it but it goes back at least to 2016 with this RFC.

There have been at least one proposal and RFC in the past that seem to be deferred or closed due to bandwidth issues.

That's what Rust does, and it's considered a problem (that the devs are regrettably unable to reasonably solve) rather than a good thing.

Lang had some conversations about this: https://github.com/rust-lang/lang-team/issues/139

The design of Rust panics unconditionally aborts the program if you panic while unwinding, and some people even want to abort if you panic in Drop.

> Better interoperability

AFAIK, the examples you give all target a basic C ABI [0] or can be made to target the same ABI. In Rust, it means targeting wasm32-unknown-emscripten

The Rust team is also working on a "WASM ABI"[1] which would be useful in taking advantage of stuff like multi-value returns, and other compilers could just choose to target that. More likely, the C ABI on WASM will be updated to account for missing features, and that'll be the standard for interoperability in the WASM ecosystem.

[0]: https://github.com/WebAssembly/tool-conventions/blob/main/Ba...

[1]: https://github.com/rust-lang/lang-team/blob/master/design-me...