dcodeIO

Thinking a bit more about how to deal with differing strong opinions in a neutral way, I think there are two valid options: * Balance: Briefly summarize both opinions if...

Please allow me a little more time to figure out if I can come up with a different structure respectively a shortened account, as I am so far not seeing...

> We could also consider adding a string.new_scalar : [i32] -> [(ref string)] right away, to address the first case. With a single operand, the behavior there should probably be...

Wondering: Would it make sense to extend this concept so any kind of host reference can be hashed / reuse what only an engine in control of the references can...

Somewhat related to #19, where in general it seems that trapping operations aren't very useful. Returning `null` seems fine to me, so an appropriate language-level exception can be thrown as...

I don't quite see how the Latin1 optimization, which is merely (a subset of) WTF-16 with the high zero byte omitted, would interfere with zero-copy? Regardless of whether an engine...

Seems reasonable to drop `string.new_utf8` and have `string.new_utf8_lossy` take its place, given that there is nothing useful one can do with a trap anyway. Perhaps, a mechanism to tell, after...

I agree that the views are odd, [as of this comment](https://github.com/WebAssembly/stringref/issues/12#issuecomment-1167944285), and would prefer a structure akin to this suggestion as well. Perhaps, could this be modeled as ``` stringref...

To me it seems that the `string.*` and `stringview_xy.*` types and operations introduce asymmetries as a result of the preference to think in terms of views - but don't necessarily...

Perhaps a fourth possibility that might have other benefits as well: Remove the views and move them as operations upon `stringref`? For instance, the two strategies for producers I see...