Ryan Hunt

> A follow up: it seems that all other WebAssembly.RuntimeErrors represent non-recoverable situations (i.e., traps). I also do not feel that issuing a JavaScript TypeError is appropriate for this situation....

I'm not sure that's any better than the current state of interop of Rust with other code on the Web today. Today you already can create a JS string from...

> For example, imagine two Wasm modules, both of which were compiled from Rust. > > Because both modules were compiled from Rust, they both internally use UTF-8 String. When...

> > I may be missing something, but if you’re compiling and linking two rust modules, why would you need JS involved at all? > > There are plenty of...

> I agree with @Pauan that linear-memory languages like Rust are highly unlikely to use stringref as their general-purpose string representation, because stringref provides garbage-collected strings. As discussed above, such...

My point wasn't that there is no value in linking together code (or in dynamic linking). My point is that to link any code together they need to share the...

> One of the goals of Wasm is to allow different Wasm modules to interop with each other, regardless of their source language, and regardless of their internal representation. >...

I want to refocus this issue on UTF-8 users of this proposal, so going back to my earlier point: Do we have any data on a managed language with UTF-8...

> I'm not aware of any concrete data so far; the Scheme-to-Wasm compiler that @wingo is working on is probably closest to being able to generate such data, but I...

> > This relies on having these operations be implemented in the host > > I strongly believe that you generally want all performance-critical "bulk" operations (processing an entire string...