Ms2ger

In https://github.com/WebAssembly/exception-handling/issues/145, it was pointed out that exception-handling and function-references were both using 0x16. Perhaps a central list of proposed opcodes would help prevent that in the future.

[web-api] Deserialization steps use undefined argument targetRealm

3

See : > If _targetRealm_’s corresponding agent cluster is not _serialized_.[[AgentCluster]], then throw a "DataCloneError" DOMException. CC @domenic

This is fixing an issue Dan caught, where it turns out that, since the global object inside the ShadowRealm is not defined using IDL, it's not an "interface" and hence...

Fixes #1136. - [ ] At least two implementers are interested (and none opposed): * … * … - [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented...

Handle conversion failures in 'upon settling'.

2

Fixes #782. *** Preview | Diff

Reorganize the Interfaces and Interface mixins sections.

3

Besides the more strict definitions of interface members and interface mixin members, this should be editorial. It is intended to make the sections flow better and to gather related content...

Explicitly include annotated types in the various type categories.

3

Fixes #670. *** Preview | Diff

Reduce the restrictions on members whose names match auto-generated properties

2

Fixes #49. *** Preview | Diff

Limit the special case in the [[Set]] algorithm to [OverrideBuiltins] interfaces

1

This is the case where it makes most sense, since the prototype chain can't shadow any properties. This change does not affect normal usage; it is only detectable by messing...

Help specifying WebAssembly.Function

2

There's a proposal to add WebAssembly.Function, which needs to kinda act like a function, but also has a static method (or an instance method) that returns the "type"; see ....