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

Thinking about the comments on ambiguity from @domenic and @annevk a bit more, I'm thinking that it could be best to switch to a model where you declare a module with an *identifier* and then refer to interfaces declared within it as `moduleIdentifer.Interface` (whether you're inside or outside of a module). It'd be really complicated to do lookup based on location, and hurt expressiveness.

The only thing I can see potentially missing is that you can't use `/` within an identifier. This can be addressed in a few different possible ways (allowing identifiers to contain `/` in general, or letting module identifers have this special right) which we could address when someone proposes a built-in module which contains `/` in its module specifier.

It'll be a little while until I have a chance to get back to this; if @Ms2ger or someone else is interested in picking this up, that'd be welcome, or otherwise I will a bit later.

-- 
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#issuecomment-473449449