Andreas Rossberg

An object can only have one runtime type. So, not all of the following statements can be true at the same time: 1. Objects of type $t and (newtype $t)...

Objects that *statically* have type (newtype $t) certainly must exist. Otherwise the type would be unusable, e.g., you could never call a function which has that as a parameter type....

Your example has no casts, so is unrelated to (3). Not sure how it is supposed to type-check, though, if $pointer and $string are (supposedly) different newtypes? Or how the...

It’s great seeing this expressivity gap in WIT addressed. However, I don’t think the proposed extension is the right solution for this. It is very special-cased and fails to address...

Shouldn't we have a corresponding test for the non-legacy instruction?

Usually one can encode such checks in Wasm itself with some wrapper function, but the start function is an interesting exception. An assert_exception might make sense, the only problem is...

For context, options of options usually come up when composing things. For example, you have some domain of values that is represented by an option (say, because it contains an...

I'm a bit confused. If you need two-phase initialisation where some init function has to be invoked *after* the instance has been fully constructed and handed out, then what keeps...

In retrospect we should have named the start function "init function", to indicate that its purpose is module initialisation, i.e., that the module isn't intended to be accessible before that...

I'd be fine with renaming in the spec. Likewise for the text format, but that might be a bit more controversial. We could allow both keywords.