- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 04 Mar 2019 01:11:50 -0800
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 4 March 2019 09:12:11 UTC
annevk commented on this pull request. > + module <mark>"std:example"</mark> { + /* module_members... */ + }; + + partial module <mark>"std:example"</mark> { + /* module_members... */ + }; +</pre> + +Note: As with partial interface definitions, partial module definitions are +intended for use as a specification editorial aide, allowing the definition +of a module to be separated over more than one section of the document, and +sometimes multiple documents. + +The order that members appear in has significance for property enumeration in +the <a href="#es-modules">ECMAScript binding</a>. I'm sorry, I don't remember that discussion, but I also don't care what method we use to determine order. What would the approach be for the separate PR? -- 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_r261971887
Received on Monday, 4 March 2019 09:12:11 UTC