Re: [heycam/webidl] [WIP] Add mixins (#433)

tobie commented on this pull request.



> +
+Each [=interface=] |I| that [=includes=] a [=mixin=] |M| must receive
+a copy of each of the [=mixin members|members=] of |M|.
+Each [=mixin member=] cooy is treated as if it had been declared on |I|.
+Its <dfn>host interface</dfn> is |I|.
+
+Note: In ECMAScript, this implies that each [=regular operation=]
+declared as a [=mixin member|member=] of [=mixin=] |M|,
+and exposed as a data property with a [=built-in function object=] value,
+is a distinct [=built-in function object=]
+in each [=interface prototype object=]
+whose associated [=interface=] [=includes=] |M|.
+Similarly, for [=attributes=], each copy of the accessor property has
+distinct [=built-in function objects=] for its getters and setters.
+
+The order of appearance of an [=includes statement=] does not matter.

What do we do with the following pre-existing sentence though (which I must have been *heavily* inspired by):

> The order of appearance of an interface definition and any of its partial interface definitions does not matter.





-- 
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/433#discussion_r142532962

Received on Tuesday, 3 October 2017 21:48:55 UTC