Andreas Rossberg

There is no law that requires all expressions to have types from the same domain (or operators on them). Many languages have multiple type domains. For example, in C++ we...

Just wanna note that the spec requires all implementations to support this, and has for years now, full stop. Either we call out implementations that don't follow this as buggy...

Drive-by-comment with my 2 cent rant: the underlying problem of so many syntax confusions is that all those languages in the C syntax tradition still decide to omit the `=`...

The main reason is that direct access to the DOM requires the ability to pass references to DOM/JS objects through Wasm. Consequently, when GC happens for JavaScript, the collector must...

> * Monotypic tuple would despecialize into fixed-length arrays of type T. That's not what you want. Tuples are accessed with a static index and no runtime overhead, easily verifiable,...

No, a list/array with fixed length is still indexed with a dynamic index, like any other list/array, which requires a check, like for any other list/array. The only difference is...

I am concerned that the idea of not allowing control flow transfer across interface boundaries (which is the what catching and coercing exceptions really means) would prevent most interesting uses...

@RossTate, not necessarily in the concrete, but abstractly they are clearly related. If we already disallow exceptions, then obviously it is hard to justify allowing the more general construct (or...

@RossTate, sorry for the confusion, my comment is tangential to the OP. It was merely a follow-up on this paragraph about exceptions from @fgmccabe's comment above: > Interface Types also...

To be clear, something that cannot be performed locally and requires global knowledge is _not_ a desugaring but a general transformation. That is a qualitative difference: desugarings are compositional with...