00:16:57  * zsocquit (Ping timeout: 240 seconds)
00:30:05  * zsocjoined
01:28:31  * zsocquit (Ping timeout: 268 seconds)
01:57:59  * not-an-aardvarkjoined
03:26:24  * zsocjoined
04:03:09  * gibson042quit (Quit: Leaving.)
06:19:29  * tobiequit (Ping timeout: 255 seconds)
06:20:26  * tobiejoined
06:39:23  * gskachkovjoined
08:44:14  * gskachkovquit (Read error: Connection reset by peer)
08:46:15  * gskachkovjoined
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
11:06:48  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
12:09:16  * gskachkovquit (Read error: Connection reset by peer)
12:09:34  * gskachkovjoined
12:19:36  * gskachkovquit (Quit: gskachkov)
12:29:32  * gskachkovjoined
12:30:20  * gskachkovquit (Client Quit)
13:26:42  * bradleymeckjoined
14:13:40  * Fishrock123joined
16:04:55  * bradleymeckquit (Quit: bradleymeck)
16:35:53  * bradleymeckjoined
16:57:29  * Fishrock123quit (Remote host closed the connection)
17:59:01  * Fishrock123joined
18:05:12  * Fishrock123quit (Ping timeout: 255 seconds)
18:52:57  <bterlson>cloudshu: pong?
19:00:06  <cloudshu>bterlson: was about the pr
19:00:58  <bterlson>#930? I replied :)
19:15:32  * chicoxyzzyjoined
19:18:52  <bterlson>is there justification for "Parse Node" over "parse node"?
19:18:58  <bterlson>is it really a proper noun?
19:19:05  * not-an-aardvarkjoined
19:22:29  <caitp>(note that an implementation is having a bit of trouble with the current #930 proposal)
19:23:09  <caitp>potential to leak cross-realm caches that might be a bit sad to fix
19:25:28  <bterlson>caitp: boo
19:25:53  <bterlson>littledan: re: #890 (Caching of template literals), this is needs consensus yeah?
19:26:33  <littledan>yeah, in particular I'm not sure if it has reasonable implications for code caching, which could be good to discuss with other implementers
19:27:00  <littledan>caitp implemented this in V8, but that was a particular question that came up, so it'd be nice to chat with others about it
19:27:46  <caitp>I'm not sure if the caching issue can ever actually happen in chromium
19:28:23  <caitp>never really heard back from daniel about that.
19:56:02  * sugendranjoined
19:57:06  * sugendranquit (Client Quit)
20:42:24  * Fishrock123joined
21:42:04  <cloudshu>caitp: wait, an implementation is having trouble with my proposal to remove "do"?
22:12:39  * bradleymeckquit (Quit: )
22:19:23  * jmdyckjoined
23:04:10  * zsocquit (Ping timeout: 246 seconds)
23:04:18  <bterlson>Domenic: re: #933, upon further inspection I'm confused by (2)
23:04:45  <bterlson>did you mean to transform between steps 2 and 3?
23:05:11  <Domenic>bterlson: step 2 is using "a promise resolved with" which is basically Promise.resolve(value)
23:05:28  <bterlson>it's the next part that confuses me
23:05:34  <bterlson>upon fulfillment of this already resolved promise
23:05:52  <Domenic>Promise.resolve(value).then(uponFulfillmentSteps, uponRejectionSteps)
23:06:20  <bterlson>don't you need the "Transforming" helper for that?
23:06:29  <Domenic>No, although I can see the confusion
23:06:36  <Domenic>Transforming is used when you care about the return value
23:06:38  <Domenic>Which turns out to be rare
23:09:53  <bterlson>yeah, I see
23:10:13  <bterlson>still concerned that it's confusing
23:11:51  <Domenic>Transforming might not pull its own weight, or might need to be done differently
23:12:10  <bterlson>I'm not necessarily arguing for transform
23:12:51  <Domenic>Yeah I'm in general very open to suggestions, as I don't think the current crop we've developed for web specs is perfect; it has weird edges and I'd be happy to get suggestions for ironing them out. Even if it's just renaming.
23:13:05  <bterlson>let me mull a bit
23:13:25  <bterlson>I also have to re-consider some things Allen has said re: how juggling execution contexts and ECMASpeak "scope" works
23:13:34  <Domenic>Oh interesting
23:13:38  <bterlson>possible we need "closing over"
23:18:46  <cloudshu>i would love for the spec to actually talk about scopes
23:18:56  <cloudshu>in a static fashion, to make the static guarantees clearer
23:22:01  * gibson042joined
23:30:34  <caitp>cloudshu: was referring to the template callsite caching change. issue # might have been wrong
23:31:49  <cloudshu>caitp: ah yeah
23:39:14  * chicoxyzzyquit (Remote host closed the connection)
23:45:04  <bterlson>What if we changed this: "Return the result of performing BindingInitialization for _lhs_ passing _nextValue_ and *undefined* as the arguments."
23:45:12  <bterlson>to: "Return BindingInitialization[Literal](_nextValue_, *undefined*)."
23:47:21  <bterlson>in specese: allow this invocation pattern for syntax-directed operations, dispense with "the result of"
23:49:52  * chicoxyz_joined
23:54:47  <Domenic>+9001
23:55:04  <Domenic>Well, not sure on the details
23:55:09  <Domenic>Where did _lhs_ go?
23:55:30  <Domenic>Also _lhs_.BindingInitialization(_nextValue_, *undefined*) seems reasonable
23:55:36  <Domenic>From how you explained it to me that once
23:56:58  <bterlson>err
23:57:03  <bterlson>Literal should be _lhs_
23:57:29  <bterlson>yeah that's another option