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

> Do you mean the "If typedKey is already a key in result," wording?

Yes.

> That's the same operation as in Map.prototype.set, which I believe we implement efficiently.

It's possible to do.  It just requires some performance/memory/complexity tradeoffs, which it's not clear to me are valuable here.

> I do think we want to avoid the possibility of a record winding up with a duplicate key

I guess the question is whether it's better to have implementation complexity/overhead to handle the rare proxy case or to have specification complexity instead.

https://dev.w3.org/html5/html-design-principles/#priority-of-constituencies would normally err on the side of specification complexity, but this is an odd case where we are likely to have more specifiers affected than implementors, so maybe this is the right tradeoff...

In any case, I just wanted to make sure we are explicitly and deliberately making this choice and understand that it's likely to cause implementation delays, in general.

-- 
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-254588848