Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Definition name uniqueness requirement omits mixins #1330

Open
bathos opened this issue Jun 25, 2023 · 0 comments
Open

Definition name uniqueness requirement omits mixins #1330

bathos opened this issue Jun 25, 2023 · 0 comments

Comments

@bathos
Copy link
Contributor

bathos commented Jun 25, 2023

In the Names section:

Within the set of IDL fragments that a given implementation supports, the identifier of every interface, namespace, dictionary, enumeration, callback function, callback interface and typedef must not be the same as the identifier of any other interface, namespace, dictionary, enumeration, callback function, callback interface or typedef.

I would have expected interface mixins to be in this list, right?

I’m almost certain that’s an accidental omission, but not 100% sure because...

...there are only two places where interface mixin names can be referenced and both are syntactically unambiguous: the second identifier of an IncludesStatement and the first identifier in PartialInterfaceOrMixin : MixinRest. So like ... technically the following fragment is already unambiguous:

interface Foo {};
interface mixin Foo {};
Foo includes Foo;

...to a computer, anyway :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants
@bathos and others