| 00:08 | <Bakkot> | devsnek very nice |
| 00:08 | <Bakkot> | devsnek you can drop the `_ref_xxxx` ones; those aren't stable anyway |
| 00:08 | <Bakkot> | for purposes of redirecting, specifically |
| 00:08 | <Bakkot> | also it'll load faster if you ship it as a string and JSON.parse it at runtime |
| 00:08 | <devsnek> | yeah I know |
| 00:09 | <devsnek> | this whole multipage project is layers of low hanging fruit lol |
| 00:36 | <jmdyck> | when github shows a commit diff, and it hides the no-diff chunks, are the "expand" widgets in the left column supposed to make them appear? If so, they're not working for me. |
| 00:37 | <Bakkot> | jmdyck yes they are, but they break for large files |
| 00:37 | <Bakkot> | including spec.html |
| 00:37 | <jmdyck> | hmph |
| 00:37 | <Bakkot> | and they break silently: they just go away rather than telling you that they're broken |
| 00:37 | <Bakkot> | it's dumb |
| 00:48 | <devsnek> | that's github for ya |
| 03:27 | <devsnek> | Bakkot: small changes https://github.com/tc39/ecmarkup/pull/237 |
| 03:37 | <Bakkot> | devsnek is there a reason to do that now instead of when adding multipage support in general? |
| 03:38 | <devsnek> | i'm not sure how to get full support done but i know that change has to be made either way |
| 03:38 | <Bakkot> | Yeah, just seems weird to add it separately |
| 17:13 | <Bakkot> | condolences to mozilla folks re: today's news :( |
| 17:45 | <bradleymeck> | have we ever seen a `class Foo { super bar = 1; }` syntax in any proposal? |
| 17:45 | <devsnek> | what does that even do |
| 17:45 | <Bakkot> | not that I recall |
| 17:48 | <bradleymeck> | devsnek: thats a good question |
| 17:49 | <bradleymeck> | i can imagine many things personally but 1 in particular is the only thing that makes sense |
| 17:49 | <bradleymeck> | but 🤷 was more curious if the space was open |
| 18:00 | <Bakkot> | devsnek do you know if discord is blocked in China? |
| 18:00 | <Bakkot> | I would expect it to be, on priors |
| 18:00 | <Bakkot> | ah, wikipedia says yes |
| 18:01 | <devsnek> | i just generally assume everything is blocked in china |
| 18:02 | <Bakkot> | freenode wasn't last I looked, IIRC |
| 18:07 | <devsnek> | it could be at any point though |
| 18:27 | <ljharb> | bradleymeck: never seen the syntax; seems like it'd be invalid in a base class and would mutate a superclass, so i'm not sure what the use case would be |
| 18:28 | <bradleymeck> | ljharb: it would mutate the superclass? |
| 18:30 | <ljharb> | that's what it suggests to me |
| 18:32 | <bradleymeck> | I could see that for `class F { super.x = 1; }` since `super.x` has meaning |
| 18:37 | <ljharb> | `super` is what imo has meaning |
| 18:37 | <ljharb> | `super()` or `super.whatever` both building off of that meaning |
| 18:41 | <bradleymeck> | ljharb: what is the meaning of `super`? since it cannot be directly assigned to a variable? |
| 18:42 | <devsnek> | this syntax should not exist |
| 18:43 | <bradleymeck> | i'm neutral to the syntax |
| 18:43 | <ljharb> | bradleymeck: it refers to the superclass. `super()` invokes the superclass constructor, `super.x()` calls the superclass prototype's `x` method, etc |
| 18:44 | <ljharb> | i'd expect `super.x = 1` to *assign* to the superclass's `x` property, and i'd expect `super bar = 1` to define and initialize the superclass' bar property |
| 21:39 | <jmdyck> | ljharb: The merge of 1908 undefined sec-validatesharedintegertypedarray, which has been in master for a few years. |
| 21:44 | <devsnek> | is undefined a verb |
| 21:45 | <TabAtkins> | yes |
| 21:45 | <Bakkot> | past participle, technically |
| 21:45 | <Bakkot> | though I guess that is a subset of "verb" |
| 21:46 | <TabAtkins> | defined is a verb, undefined is a stadnard construction over that |
| 22:10 | <ljharb> | jmdyck: the diff has `oldid="sec-validatesharedintegertypedarray"` but maybe only `oldids` is valid? |
| 22:10 | <Bakkot> | yeah it's oldids |
| 22:11 | <Bakkot> | I have a note to lint this but haven't gotten to it yet :( |
| 22:12 | <ljharb> | k, all fixed |
| 22:40 | <TabAtkins> | Ah, I should lint that in Bikeshed, since I'm the one who introduced it and then ecmarkup took it too. |
| 22:45 | <Bakkot> | my plan is to have an explicit list of the expected attributes (at least for certain tags) and error out if you have any unexpected ones |
| 22:45 | <Bakkot> | s/error out/warn/, which will fail the build if you pass `--strict` |
| 22:46 | <Bakkot> | (or at least it will once I can convince michael to review https://github.com/tc39/ecmarkup/pull/235 so I can cut a release) |
| 22:55 | <ljharb> | sounds like the right plan |