Re: [heycam/webidl] Define Web IDL Modules (#675)

Ms2ger commented on this pull request.



> @@ -801,11 +807,32 @@ expected that an object that implements a particular IDL interface
 provides ways to inspect and modify the object's state and to
 invoke the behavior described by the interface.
 
+[=Interfaces=] and [=partial interfaces=] have an <dfn for="interface,partial interface">enclosing
+module</dfn>, which is a [=module=] or null.
+Unless otherwise specified, it is null.
+
+<div algorithm>
+  [=Interfaces=] and [=partial interfaces=] have a
+  <dfn for="interface,partial interface">scoped identifier</dfn>,
+  which uniquely identifies an [=interface=].

Changing how LegacyNamespace works in this PR seems out of scope to me. Note that, if I connected everything correctly, using the qualified name would mean you'd need changes like this to specifications that use it:

```diff
 namespace WebAssembly {
-    Promise<Module> compile(BufferSource bytes);
+    Promise<WebAssembly.Module> compile(BufferSource bytes);
 };
```

Maybe we want that, but let's discuss that separately.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/pull/675#discussion_r274820577