Re: [whatwg/webidl] Defining AbstractModuleSource intrinsic inheritance (Issue #1322)

Declarative comment / prose text “overrides” both have an unclear relationship to the imperative realm-initializing algorithms in Web IDL (_when_ do the “overrides” happen?) and make it impossible for tooling that consumes Web IDL fragments to know about exceptional cases without hard-coding knowledge of the special cases. Since I work on that kind of tooling, I’m biased to prefer an extended attribute solution.

In the past I think some EAs that aren’t _quite_ “legacy” were given the `Legacy` prefix to discourage new “unbridled” usage?

If a non-IDL solution is used, then it would suggest to me that the existing imperative step for taking care of DOMException...

![3.7.3. Interface prototype object, “create an interface object,” step 4](https://github.com/whatwg/webidl/assets/6257356/e25c40c0-7d1e-40d8-be94-efd8ca1759c5)

...would want to be removed? Or is the idea that the “create an interface object” algorithm would introduce a new step like this for `WebAssembly.Module` even though the interface is defined elsewhere?

BTW I think there is another example of this that’s also in WebAssembly? The NativeError-template Error classes. I’m unsure if they would benefit, but they do use use %Error%/%Error.prototype%.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/1322#issuecomment-1595032817
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/issues/1322/1595032817@github.com>