Andreas Rossberg

Ah thanks. (1) is fixed in https://github.com/WebAssembly/spec/commit/6e4c4bcaf7a4747f7a13623889727ee117550336. Re (2), that should actually be working as intended, since the side condition (𝑓𝑢𝑛𝑐 = func 𝑡𝑦𝑝𝑒𝑖𝑑𝑥 𝑙𝑜𝑐𝑎𝑙* 𝑒𝑥𝑝𝑟)* already implies the constraint...

The problem with such a test is that engines can legally fail it, due to (legal) implementation or resource limits. And most likely, such engines (will) exist, even when they...

I have a vague recollection that we discussed supporting the respective top types, i.e., add anyref, as part of the minimal JS API MVP, but defer the rest to later....

The latter probably is the result of semi-mechanically adding exnref to all the places where v128 is ruled out. In some of them it is redundant (though harmless, and potentially...

I'd definitely include anyref and funcref. Not sure about exnref, given that it cannot be passed to JS in the first place, but I guess it would be consistent with...

The wasm-3.0 branch (which will be merged into main very soon in one form or the other) doesn't actually change the test structure, it merely has additional proposals merged. Some...

I moved exceptions and memory64 tests to their own directory in #1951.

@bvisness, guards would make sense to me, though since it's meta-information, I'd use annotation syntax for that: `(@if-supports "multi-memory") (module ...)`. But yeah, marking up the entire test suite would...

Sounds okay as a low-key solution. To be honest, anything more formal (like annotating tests with "features") would only make sense to me if we adopted respective profiles that properly...

> On a related note, why are block types valid as instruction types when they cannot describe locals indices? Shouldn't they be valid as function types instead? Either is fine,...