Ingvar Stepanyan

Btw, this is not true on the Rust side, and there you should always use explicit `&[T; N]` in FFI interface, since for just `[T; N]` it chooses between pass-by-value...

Yeah, a warning/error would be good (even better would be if Rust compiler would do the same).

After thinking about this a bit more, I think the best solution here would be to use the common `bytes` crate: https://docs.rs/bytes/latest/bytes/struct.Bytes.html It allows to wrap arbitrary buffer types, provides...

> It generates TypeScript based on serde and uses `serde_wasm_bindgen` for ABI conversions. FWIW there's also [tsify](https://github.com/madonoharu/tsify), which does this as well.

@Cldfire FWIW that comment above was mistaken, DWARF does work well with Chrome directly: https://github.com/rustwasm/walrus/pull/231#issuecomment-1431619795

@connor4312 It looks like the call stack name is not taken from DWARF but rather from the names section? Is that a currently known limitation?

Ah weird, could be. It's been couple of years since I tried Rust-produced Wasm in DevTools. I guess they'd need Rust-specific demangling to omit it. Not a big deal either...

> So it's not just a problem of functions missing from the wasm file, it's a problem of playground somehow not finding the output that was produced. Well, yes. What...

With that in mind, one workaround I found since is that you can explicitly specify ```rs #![crate_type = "cdylib"] #[no_mangle] pub extern fn foo() {} ``` and then output will...

Probably. Back when I submitted issue I didn't know it works at least sometimes (like when you have `main`), but now given the symptoms this seems like a reasonable conclusion.