2026-11-02 [09:42:41.0744] The ecma262 IPR check is currently failing because of a commit of a collague of mine that is not a delegate. I wonder if we could have a GH team for "not a delegate, but still employed by a member organization"? [09:57:47.0626] we could. i already asked him to register tho [09:57:49.0811] * we could. i already asked him to register tho ( https://tc39.es/agreements/contributor/ ) [09:59:14.0437] I can also make him a delegate if it's easier. I don't think the RFTG form is the right tool for this, since he's not contributing on his behalf but on behalf of Igalia? [09:59:51.0953] i'm not sure it matters as long as it comes in without patent burdens, which igalia already covers anyways [10:00:00.0733] that would also be fine tho, to make him a delegate [10:50:08.0280] It is easier for members to make their folk delegates. The form is trivial and Jordan’s SLA for processing it is better than ’s uptime. And the benefit is we avoid any potential conflict over whether contributions are at odds with the member. And the individual gets greater access to resources like the reflector. 2026-11-05 [15:25:38.0591] Chris de Almeida, Richard Gibson: at the last meeting Chris mentioned "hand wavy concerns about interop" with regards to pulling AbortController into the core JS language. do you recall any details there? 2026-11-10 [17:30:50.0423] my understanding is that it's primarily just about DOMException [17:35:21.0425] There's some concern around EventTarget also [17:35:49.0419] At least, I've got concerns about it, that is [17:47:58.0821] The plan is to allow hosts to define the superclass and add initialization, but not actually use any of that machinery [17:48:21.0653] Similarly the error is just "a host defined error whose name is AbortError" or something [17:48:43.0255] Are there concerns with that approach? [17:49:18.0757] Though ideally we'd convince the web to upgrade AbortError to a real class, they've done that before, just some web compat risk [17:51:07.0521] If we are able to make progress on the code property for errors, what would the code property be for AbortError 2026-11-11 [07:38:38.0001] We have started to get multiple spam posts on https://es.discourse.group/ every day. they always follow the same format: new user, first post, reply to existing thread, says something a bit related to the thread but mostly confusing tech speak and then something like: "more thoughts here:" and a link like: something.pages.dev/r/es_discourse_group [07:39:35.0430] I've been manually flagging them when I noticed the notification. I'm wondering if the admins have more tools at their disposal to block these? [07:41:22.0271] I thought the site used to have some level system where you couldn't post links until you have met certain trust levels. Though maybe that was just the ability to edit posts [09:31:48.0879] so you know how `async function*(){ yield 0; }` does an `await` at the `yield`? what if we checked if the value was thenable and skipped the `await` if not? we're still returning a Promise either way so I don't think there's any zalgo issues, just fewer microtask ticks [09:38:41.0567] I guess if there's already another call to `.next()` queued we'd need to re-introduce that tick to avoid `foo; yield; baz;` potentially running `foo` and `bar` in the same tick, which is mildly annoying but whatever [09:42:08.0568] I wish we'd put a little more effort into minimizing the amount of this machinery; really gotta get https://github.com/tc39/proposal-faster-promise-adoption/issues too [09:49:47.0509] also https://github.com/tc39/ecma262/pull/3689 [10:16:41.0799] > <@aclaymore:matrix.org> I've been manually flagging them when I noticed the notification. > I'm wondering if the admins have more tools at their disposal to block these? I’ve looked, but i can’t seem to edit the “blocked URLs patterns” so all i see is reactive approaches [10:34:24.0404] Thanks for checking [10:48:48.0515] Yeah sorry I've had 0 time to work on this. [12:30:42.0800] k i think i may have autoblocked the url pattern they use 2026-11-12 [16:49:17.0466] > <@bakkot:matrix.org> so you know how `async function*(){ yield 0; }` does an `await` at the `yield`? what if we checked if the value was thenable and skipped the `await` if not? we're still returning a Promise either way so I don't think there's any zalgo issues, just fewer microtask ticks https://github.com/tc39/ecma262/pull/4078 [05:52:35.0011] could someone please do the stage 4 update & archival for https://github.com/tc39/proposal-dynamic-code-brand-checks [05:54:31.0060] I updated the readme but cannot archive [06:02:34.0126] same for iterator chunking and includes ([Michael Ficarra](https://matrix.to/#/@michaelficarra:matrix.org)) [07:58:42.0281] done, thanks for the reminder [07:58:54.0206] I kept remembering I had to do it, then getting distracted and forgetting again [10:04:28.0758] Could somebody add the next meeting to the calendar? :) 2026-11-17 [01:54:50.0543] If the person that usually does it cannot do it at the moment, could I get write access to the calendar? [13:33:15.0891] yep, i'll take care of it [13:42:28.0382] all done [14:31:08.0071] Thank you! :)