| 05:12 | <bendtherules> | Did something change recently about the spec html? In ecmarkup or something? |
| 05:12 | <bendtherules> | On mobile, navigating the doc and specially the sidebar search has become sooo much slower. No debounce, etc? |
| 05:12 | <bendtherules> | Might be something that chrome (on android) has changed though. |
| 05:15 | <Bakkot> | I don't believe so, no |
| 05:15 | <Bakkot> | it's always been slow in chrome; it's much, much better in firefox |
| 05:17 | <bendtherules> | Firefox mobile? |
| 05:18 | <devsnek> | yeah |
| 05:18 | <devsnek> | also large diffs on github |
| 05:18 | <devsnek> | freeze chrome but do fine on firefox |
| 05:27 | <bendtherules> | Yeah, firefox is working better. The view is little zoomed out compared to chrome, but definitely manageable. |
| 15:38 | <bendtherules> | Question - In try..finally, why does finally's (non-normal) completion record take precedence, even when try is throwing? |
| 15:39 | <bendtherules> | Finally can effectively then act as a catch sometimes. Where can i find the discussion logs for finally in try? |
| 15:53 | <Bakkot> | this is an ancient decision, almost certainly copied from Java, which probably copied it from something else before it |
| 15:54 | <Bakkot> | you'd have to go back to some mailing lists from the 80s, I expect |
| 15:54 | <Bakkot> | if it's captured anywhere |
| 15:54 | <bendtherules> | haha, got it :) |
| 15:59 | <Bakkot> | that said, I think it's pretty natural: if I write `function f(){ try { return x; } finally { doSomething() } }`, and `doSomething()` throws, I don't want that function to just return without throwing |
| 16:00 | <bendtherules> | What about `function f(){ try { throw x; } finally { return y; } }`? I would expect finally to not act suppress the error - that behaviour is somewhat implicit here |
| 16:01 | <Bakkot> | I do not have that expectation I guess |
| 16:01 | <bendtherules> | *not suppress |
| 16:01 | <bendtherules> | ok, fair enough |
| 16:01 | <Bakkot> | and also do not expect that code to come up nearly as often |
| 16:06 | <bradleymeck> | shu: https://docs.google.com/presentation/d/19S97ZqhibJABqzeP5ZU6Flk6TVgWzXuvJWFbNTTfpWs/edit#slide=id.g8d8a4d4a81_0_377 also affects node you might note |
| 18:04 | <shu> | bradleymeck: will try to remember by monday but if it slips my mind please call it out during my preso? |