02:58:15  * bobmcw_joined
02:59:58  * bobmcwquit (Ping timeout: 252 seconds)
02:59:58  * AKPWDquit (Ping timeout: 252 seconds)
03:04:56  * AKPWDjoined
04:02:41  * esasquit
04:36:28  * BobGneujoined
05:23:18  * xaxxonjoined
06:24:21  * RT|Chatzillaquit (Read error: Connection reset by peer)
06:25:44  * trigenquit (Quit: ZNC - http://znc.in)
06:25:55  * trigen-joined
06:28:05  * RT|Chatzillajoined
06:29:24  * RT|Chatzillaquit (Excess Flood)
06:29:40  * dagobert___joined
06:33:09  * dagobert__quit (Ping timeout: 240 seconds)
06:33:24  * dagobert___changed nick to dagobert__
07:25:11  * BobGneuquit (Ping timeout: 240 seconds)
07:54:30  * plutoniixquit (Quit: Leaving)
08:36:41  * stalledquit (Ping timeout: 255 seconds)
08:45:36  * plutoniixjoined
08:51:44  * stalledjoined
09:16:56  * Tweth-V-PDSjoined
09:19:09  * Tweth-U-PDSquit (Ping timeout: 240 seconds)
09:33:48  * RT|Chatzillajoined
09:42:16  <schuay>caitp: the JS debugging API will also be removed soon, inspector protocol is the future. there's a bit of documentation at https://github.com/v8/v8/wiki/Debugging-over-the-V8-Inspector-API
09:51:36  * Net147quit (Ping timeout: 240 seconds)
09:54:17  * Net147joined
10:11:20  <trungl-bot>Tree closed by machenbach@chromium.org: closed - maintenance
10:22:44  * rakucopart
10:34:58  * Keverwjoined
10:46:32  <trungl-bot>Tree opened by machenbach@chromium.org: open
10:54:48  * Net147quit (Quit: Quit)
10:56:48  * Net147joined
11:33:49  * plutoniixquit (Quit: Leaving)
12:34:55  * xaxxonquit (Read error: No route to host)
14:02:15  * bobmcw_changed nick to bobmcw
14:02:15  * bobmcwquit (Changing host)
14:02:15  * bobmcwjoined
14:57:25  * joyeejoined
16:14:03  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
16:49:58  <trungl-bot>Tree closed by buildbot@chromium.org: closed (http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20builder/builds/19491 from eb5915b42855bfbac90cef78017767b6b6f85629)
17:23:51  * joyeequit (Read error: Connection reset by peer)
17:24:25  * joyeejoined
17:47:38  * joyeequit (Read error: Connection reset by peer)
17:47:47  * joyeejoined
18:04:27  <trungl-bot>Tree opened by machenbach@chromium.org: open
18:08:50  * plutoniixjoined
19:12:47  * xiinotulpjoined
19:15:39  <jwolfe>i found the problem i was having yesterday. the heuristic in ParserBase::ParsePrimaryExpression() that flags "(function..." for eager parsing wasn't noticing "(async function". I can submit CL to "fix" this heuristic, and it would fix a bug in my F.p.toString/CreateDynamicFunction CL.
19:16:14  * plutoniixquit (Ping timeout: 260 seconds)
19:17:10  <jwolfe>i say that, and then it's causign test failures. hm....
19:23:27  <jwolfe>well, that caused a failure for test262/language/expressions/async-function/early-errors-expression-formals-body-duplicate, and i think it's because the SyntaxError isn't an early error anymore, it's just a normal error. but i think that's because we're not running the preparser at all, due to the heuristic. i might need some help to understand all this
19:37:53  * joyeequit (Read error: Connection reset by peer)
19:38:23  * joyeejoined
20:06:32  <caitp>jwolfe: usually we have problems with syntax errors not being early _because_ the preparser ran, not because it didn't run
20:06:51  <caitp>EG the preparser doesn't do the same tracking that the parser does, so it can't emit some early errors
20:07:36  <jwolfe>oh. that test is actually marked to fail in the status file
20:07:43  <caitp>yeah, so that's the issue
20:07:54  <caitp>good job, nice find :)
20:11:55  <littledan__>yeah, a CL to fix the heuristic sounds great
20:12:10  <littledan__>we already know that the preparser doesn't check for duplicate parameters, and the parser does, so that test262 behavior is expected
20:12:52  <littledan__>it's fine to add and remove failure expectations for a test like that, as heuristics change and the error comes at the right or wrong time
20:14:00  <caitp>although, you could argue we're only fooling ourselves by marking the test as passing, since we know it doesn't "really" work
20:14:15  <caitp>as soon as the preparser kicks in
20:15:32  <jwolfe>yeah. the test would only work because that particular test was written with a '(' before the "async function". other functions like that one are written with "0, " instead, and that would still be a failure.
20:17:43  <caitp>I think JSC does the duplicate parameter checking in SyntaxChecker mode (their version of "preparsing"), but fails some other things like an early error for invalid assignment targets
20:17:58  <caitp>probably no vm gets it completely right, and it's hard to check every possible case
20:18:46  <jwolfe>should i submit a separate CL for the heuristic fix, since it's not actually that related to my other CL?
20:20:55  <caitp>go for it
20:24:59  <caitp>separate CL i mean
20:28:55  * Guest59_joined
20:31:15  * Guest59quit (Ping timeout: 258 seconds)
20:51:34  * joyeequit (Remote host closed the connection)
20:52:10  * joyeejoined
20:56:13  * joyeequit (Ping timeout: 240 seconds)
21:40:31  * joyeejoined
21:45:33  * joyeequit (Ping timeout: 276 seconds)
22:10:54  * xiinotulpquit (Quit: Leaving)
22:57:28  * RT|Chatzillajoined
23:36:36  * Cube8joined
23:37:35  * Guest59joined
23:39:53  * Guest59_quit (Ping timeout: 240 seconds)
23:59:57  * plutoniixjoined