| 12:12 | <JakeA> | If a realm only has one instance of a particular object (enforced through the spec), is it ok to say "Let |foo| be the only instance of {{Foo}} within |realm|"? |
| 13:02 | <Domenic> | JakeA: seems unambiguous, but also unlikely to match how implemenations will do things, so meh? |
| 13:07 | <JakeA> | I'll take "meh" until implementations guide towards something better. |
| 14:04 | <Domenic> | I mean, seems like it would be pretty standard to say "each WindowOrWorkerGlobalScope has a <dfn>foo</dfn>, an instance of {{Foo}}" |
| 15:58 | <JakeA> | Yeah, that might make more sense |
| 15:59 | <JakeA> | Is there a definitive on null vs undefined? When to use one or the other |
| 16:21 | <TimothyGu> | JakeA: `undefined` doesn't exist in spec land |
| 16:21 | <TimothyGu> | IDL converts it to null usually |
| 16:22 | <TimothyGu> | and in certain cases (dictionary, overload resolution) it's called "not present" |
| 16:23 | <TimothyGu> | (Not sure if that's what you're asking) |
| 16:57 | <Domenic> | JakeA: yeah it's pretty bad right now. Most places use null because that's all that exists. A few places started using undefined to be more consistent with ES, e.g. on get() return values from map-esque things. Now it's just inconsistent.... |
| 18:12 | <Domenic> | Hmm what would you call the boolean (not flag) version of "transient activation flag" |
| 19:32 | <TabAtkins> | JakeA: What Domenic said, but I'd match ES conventions if possible. Unfortunately that means having operations return `any` and then clarify in prose; when I've done this I've put a comment in the IDL explaining it. |
| 19:33 | <TabAtkins> | https://github.com/heycam/webidl/issues/60 |
| 21:08 | <jyasskin> | JakeA: What are you using null vs undefined for? A not-present value for an Infra-struct's items, or something that'll be exposed to JS? |