Francis McCabe
Francis McCabe
this is still under discussion.
Essentially the interface types and core wasm types are distinct. So i32 would need to be coerced to either signed or unsigned. The rationale is that core wasm types are...
There is a special situation with f32/f64; but otherwise there should be no overlap between the two schemas. EIther a function has an interface type signature or a core wasm...
Yes, that 'spreading the memory' disease also worries me. There is a better alternative: memory views. It is better for two main reasons: it accounts for more use cases than...
1. Record.lift/lower (not my preferred names for these ops) wrap and unwrap interface value types. I.e., they go from a sequence of IT values on the stack a single IT...
Prefer pack and unpack but not super committed to that
This is perfectly reasonable: to have more than one coercion operation. That is one of the fundamental merits of the adapter fusion approach. There is, of course, a counter argument:...
Depends on what the goal is. If maximum interoperability is then canonicalization seems essential
Yes. I think that this is right for booleans. There are other cases to consider: optional types, promises, days of the week, error codes...
On Thu, Jul 25, 2019 at 2:52 AM Olivier FAURE wrote: > For more general ADTs, such as a Either a b = Left a | Right b, that >...