Ingvar Stepanyan

I wonder how hard is it to just fix this on wasm-bindgen side? Does it require major version bump because older wasm-bindgen is expected to work against newer projects or...

> I have not personally put that much effort into fixing this. The ABI was likely to change anyway with multi-value now stabilizing so it didn't seem to pressing to...

My one concern with allowing arbitrary `: Into` is that it ends up easily encouraging throwing non-`Error` objects on JS side, which is a serious antipattern as it loses entire...

The docs need to be updated, as https://rustwasm.github.io/wasm-bindgen/reference/types/result.html still says only `Result` is supported. If I didn't stumble upon this PR, there would be no way of knowing this is...

@Pauan Aside from performance difference, it's important to consider a usecase of infinite iterators too - these are not completely uncommon in lazy scenarios, and wouldn't be possible to collect...

Although, rather than solving this particular issue on its own, it seems to be a narrow case of a potentially more general "allow exposing `Box` to JS", which could be...

As another use-case, I think tuples support could improve interfaces for js-sys iterators too. In particular, `.entries()` on `Map` / `Set` / `Array` could produce an iterator over tuples of...

Just an update - I imagine this might become easier these days (or, at least, soon) by leveraging multi-value Wasm feature.

> but none of the standard library or cargo packages. They are all prefixed like `/cargo/...` or `/rustc/...` It's expected and happens because standard library in Rust is prebuilt on...

> But, either way, the breakpoints won't work at the moment because, as mentioned above, DWARF remapping is not implemented in wasm-bindgen. Should probably clarify that this is only if...