You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, JS.md refers to Web.md to define names. That document just seems to say, decode the names as UTF-8 into UTF-16 and throw eagerly on any validation errors when validating the module as a whole. Is that right? A couple questions:
Is there a particular reason this is in Web.md and not JS.md, and says "on the Web"? It's hard for me to understand which part of any of this would be skipped in other environments where WebAssembly is used. For example, wouldn't Node.js want to do all of the same things?
Does that conversion algorithm do anything additional besides throw on invalid UTF-8? Why not just say, "throw on invalid UTF-8"?
The text was updated successfully, but these errors were encountered:
The Web.md and JS.md bits you're referring to predate the more recent agreement and PR that all strings must be valid utf-8 in wasm. So we can probably nuke this "Names" section in Web.md and the JS-API spec can point to the core spec requirement.
Yeah, the conversion algorithm was I suppose just written that way to be concrete, I guess.
Right now, JS.md refers to Web.md to define names. That document just seems to say, decode the names as UTF-8 into UTF-16 and throw eagerly on any validation errors when validating the module as a whole. Is that right? A couple questions:
The text was updated successfully, but these errors were encountered: