Re: [heycam/webidl] Declaring modules in WebIDL (#592)

> As for a notion of fully qualified name, how would qualified name be? This is what determines the name for @@toStringTag, but it seems like it'd be unique enough to me.

Interesting. I see per the PR the @@toStringTag for the examples would be `"std:dom2.Node"`?I'm not sure how I feel about that, although in general I'm not sure how I feel about `@@toStringTag` usage at all. (I vaguely would prefer we stopped using it for new things, maybe.)

> Do you think there are ever use cases where you'd shadow a name defined globally with one that's local to a module, and still want to refer to the global one within that module?

I can definitely think of cases, e.g. defining a modern type in a module and wanting to add a utility method to convert from the legacy global type to the modern type. But, I think it is fine for an MVP to not allow such references, and add syntax for them when we actually encounter such cases.

-- 
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/issues/592#issuecomment-469814469