2025-05-12 [07:31:27.0961] If people are available today, I would like to meet briefly to check if we think it's reasonable to present at the next meeting or push to the one after [07:42:45.0126] I’ll be there, a few minutes late. (and i think the one after) [08:01:16.0409] I'll join momentarily 2025-05-13 [12:07:03.0531] Hiya! I'm planning to submit a proposal at the next plenary for assertions (or the problem it solves), and I think it will have some overlap with pattern matching. Bringing it up here so it's on your radar and in case you have any comments https://github.com/JakobJingleheimer/proposal-assertions 🙂 [15:26:38.0371] jakobjingleheimer: Hm, I don't immediately see the connection. Enlighten me? [15:50:54.0776] eg `assert.equal(typeof x.foo, 'boolean');` and `match (x) { when { foo: boolean } {} }` are equivalent, aside from error message [15:51:04.0029] * eg `assert.equal(typeof x.foo, 'boolean');` and `match (x) { when { foo: boolean }: {} }` are equivalent, aside from error message [15:51:13.0213] * eg `assert.equal(typeof x.foo, 'boolean');` and `match (x) { when { foo: boolean }: {} }` are equivalent, aside from error message (ignore any syntax mistakes, it's off the cuff) [16:31:41.0258] Oh, sure, I guess, but just using a `when` like that just for an assertion isn't really the intended usage. (It won't even give you a very good error message, just the generic "fell off the end" error.) I don't think it really overlaps in practice. 2025-05-14 [17:06:59.0648] > <@ljharb:matrix.org> eg `assert.equal(typeof x.foo, 'boolean');` and `match (x) { when { foo: boolean } {} }` are equivalent, aside from error message assert(x.foo is Boolean) [17:07:05.0457] this will look better [17:07:15.0125] sure, that one too [17:07:44.0427] even just `x is (pattern) || throw y` assuming we have throw expressions 2025-05-22 [09:54:40.0047] both for plenary week and memorial day, i'm going to cancel next monday's meeting