- From: Daniel Ehrenberg <notifications@github.com>
- Date: Wed, 12 Dec 2018 09:11:06 -0800
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 December 2018 17:11:28 UTC
I've observed accidental exposure of public APIs in early draft specifications due to the lack of this feature as well. What was the motivation for creating all of these implicit slots, and then needing a `[NoSlot]` extended attribute? How about we just make all these slots explicit? As for type system, I like the idea of keeping these internal slots untyped (matches current usage). Could we make the ECMAScript undefined value the default (matching current usage), or would this be too big of a layering violation given how we don't have `undefined` in WebIDL yet? Minor: ECMAScript switched to internal slots all starting with a capital letter. Now, lower case internal slot names look ugly to me. I'm fine with using lowercase if others prefer it, though. -- 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/495#issuecomment-446666448
Received on Wednesday, 12 December 2018 17:11:28 UTC