| 01:57 | <rkirsling> | hmm if you make a ticket you can CC me since I did that feature |
| 03:02 | <rkirsling> | what was the point of misunderstanding though, I wonder? |
| 03:04 | <rkirsling> | oh literally something about the productions themselves, huh |
| 03:19 | <rkirsling> | that really kinda sucks actually. I thought one was free to view #x in like a "decorated" unary op |
| 05:15 | <Ashley Claymore> | It seems that at least 4 people (including me) all made the same/similar mistake |
| 05:15 | <Ashley Claymore> | Productions be hard 😅 |
| 05:15 | <rkirsling> | I'm not even sure how to describe the mistake though |
| 05:16 | <rkirsling> | like this is genuinely tricky to even wrap your head around in terms of precedence |
| 05:16 | <rkirsling> | my solution is gonna be grotesque |
| 05:20 | <Ashley Claymore> | TypeScript is going with initially parsing as (x << #id) in v and then the next stage spots/emits the error. Though I have zero knowledge of jsc’s code so no idea if that approach applies. Or if SyntaxErrors must come from the first parse pass |
| 05:29 | <rkirsling> | ah right, I think I'd somehow convinced myself that it needed to be part of the first pass |
| 05:30 | <rkirsling> | brain too tired for this, apparently |
| 06:06 | <rkirsling> | er hmm no I take that back |
| 06:08 | <rkirsling> | yeah I really think the way we have it I basically have to check not only that the next token is in but also that the current operator on top of the stack (if any) has precedence less than < |
| 06:09 | <rkirsling> | ("grotesque" may be a bit dramatic; it's just unlike any other case 😅) |
| 06:10 | <rkirsling> | ...this would've been a good use for the #tc39-implementers:matrix.org channel, heh |
| 06:58 | <Ashley Claymore> | I've joined that channel now. Thanks, wasn't aware of it 🙂 |
| 14:50 | <jschoi> | There’s a TC39 Research Call scheduled to start right now, but Zoom says the host hasn’t started the meeting. Is anyone else in the meeting yet? |
| 14:51 | <ptomato> | I was also wondering that |
| 14:54 | <Jack Works> | There’s a TC39 Research Call scheduled to start right now, but Zoom says the host hasn’t started the meeting. Is anyone else in the meeting yet? |
| 14:54 | <Jack Works> | 👀 |
| 14:55 | <jschoi> | Ah, so no one else can start the meeting, I presume… I wonder if Felienne Hermans, the researcher, is aware of this too? |
| 14:59 | <Jack Works> | We can have an 1hr holiday too 😋 |
| 15:00 | <littledan> | FYI the agenda for the incubator call in an hour is now posted at https://github.com/tc39/incubator-agendas/blob/master/2021/09-20.md |
| 15:00 | <littledan> | Hope to see you there soon! |