Re: [heycam/webidl] Specify open dictionaries. (#180)

> Choosing a different name for open and closed dictionaries doesn't help here.

The question is whether it helps with specification clarity.  It's possible that using the same name for the two things is ok if it makes the spec simpler, or that it makes things more complicated because now whenever you mention a dictionary you have to make it clear which one.

It's also _really_ confusing, in my opinion, that one of these is just a type and the other is a named construct that involves inheritance, etc.

So if we're serious about the half-open bit: what are we thinking of as the syntax for those?  Because it's worth thinking about that up front a bit if that's the real end goal, so we don't end up with weird contortions later with named type definitions inheriting from unnamed types and whatnot, like some of the proposals I've seen floating around.

-- 
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/180#issuecomment-252922117