[00:02] <[Coke]> can someone bump to get the mimalloc changes for next blin?

[01:35] <[Coke]> oh, that was just a PR.

[01:50] <Geth> ¦ nqp/main: ed3e57ba17 | (Will Coleda)++ | tools/templates/MOAR_REVISION

[01:50] <Geth> ¦ nqp/main: Bump MoarVM - Bump mimalloc to v2.4.1

[01:50] <Geth> ¦ nqp/main: review: https://github.com/Raku/nqp/commit/ed3e57ba17

[01:52] <Geth> ¦ rakudo/main: 73a74b5f86 | (Will Coleda)++ | tools/templates/NQP_REVISION

[01:52] <Geth> ¦ rakudo/main: Bump NQP - Bump mimalloc to v2.4.1

[01:52] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/73a74b5f86

[03:44] <Geth> ¦ rakudo: ugexe++ created pull request #6454: RakuAST: emit callstatic for named sub calls with bound-once callees

[03:44] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6454

[04:35] <Geth> ¦ rakudo: ugexe++ created pull request #6455: RakuAST: reduce a smartmatch against a type object to a type check

[04:35] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6455

[05:23] *** [Coke] left
[05:28] *** [Coke] joined
[05:37] *** hurufu joined
[06:26] *** finanalyst joined
[08:14] *** finanalyst left
[08:23] *** finanalyst joined
[10:07] *** finanalyst left
[17:31] <ugexe> anyone wanna make a new release of https://github.com/raku-community-modules/NativeHelpers-Blob/ ? the rakuast fix PR was merged. i'd try to do it but i'm not familiar with the .META/SOURCE.cdn.json stuff

[18:02] <[Coke]> failed its windows test?

[18:46] <japhb> [Coke]: Has been failing its windows test the whole time.  :-(

[18:51] <lizmat> I'dd do a release

[18:51] <lizmat> *'ll

[18:53] <ugexe> lizmat++

[18:55] <Geth> ¦ rakudo/main: 9e2652bf15 | (Nick Logan)++ (committed using GitHub Web editor) | 3 files

[18:55] <Geth> ¦ rakudo/main: RakuAST: reduce a smartmatch against a type object to a type check (#6455)

[18:55] <Geth> ¦ rakudo/main: 

[18:55] <Geth> ¦ rakudo/main: Previously a smartmatch always compiled to a call of the setting's

[18:55] <Geth> ¦ rakudo/main: infix:<~~>, which dispatches ACCEPTS and boolifies its result. When the

[18:55] <Geth> ¦ rakudo/main: matcher is a compile-time known type object the legacy optimizer

[18:55] <Geth> ¦ rakudo/main: instead emits a plain nqp::istype of the topic, which answers

[18:55] <Geth> ¦ rakudo/main: identically: istype runs a subset's refinement and honors definite and

[18:55] <Geth> ¦ rakudo/main: <…commit message has 16 more lines…>

[18:55] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/9e2652bf15

[18:55] <Geth> ¦ rakudo/main: 0587f61be6 | (Nick Logan)++ (committed using GitHub Web editor) | 2 files

[18:55] <Geth> ¦ rakudo/main: RakuAST: literalize an unhandled node to the sentinel, not a die (#6452)

[18:55] <Geth> ¦ rakudo/main: 

[18:55] <Geth> ¦ rakudo/main: Previously the catch-all literalize candidate died with "literalize on

[18:55] <Geth> ¦ rakudo/main: <type> NYI". That die is not a CannotLiteralize, so the proto's CATCH

[18:55] <Geth> ¦ rakudo/main: could not turn it into the sentinel and it leaked out. Building an

[18:55] <Geth> ¦ rakudo/main: indirect package name from a runtime expression then reported "literalize

[18:55] <Geth> ¦ rakudo/main: on RakuAST::Ternary NYI" instead of that the name is not compile-time

[18:55] <Geth> ¦ rakudo/main: <…commit message has 6 more lines…>

[18:55] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/0587f61be6

[18:55] <Geth> ¦ rakudo/main: 54bd488246 | (Nick Logan)++ (committed using GitHub Web editor) | 2 files

[18:55] <Geth> ¦ rakudo/main: RakuAST: dispatch native-typed constants as native (#6450)

[18:56] <Geth> ¦ rakudo/main: 

[18:56] <Geth> ¦ rakudo/main: Previously a reference to a native-typed constant compiled to a lexical

[18:56] <Geth> ¦ rakudo/main: lookup of the boxed value, so `my int constant PICK = 0; foo PICK` passed

[18:56] <Geth> ¦ rakudo/main: an Int and could never select a `foo(int)` candidate. A native multi

[18:56] <Geth> ¦ rakudo/main: candidate is only chosen when the argument is intrinsically native at the

[18:56] <lizmat> ARGH,   looks like the cert on 42.zef.pm has expired

[18:56] <Geth> ¦ rakudo/main: call site, the way a `my int $x` read is; a boxed lookup never qualifies.

[18:56] <Geth> ¦ rakudo/main: <…commit message has 9 more lines…>

[18:56] <lizmat> ugexe ^^

[18:56] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/54bd488246

[18:57] <Geth> ¦ rakudo/main: 2e49395508 | (Nick Logan)++ | 2 files

[18:57] <Geth> ¦ rakudo/main: Make Format.new record its directives reliably

[18:57] <Geth> ¦ rakudo/main: 

[18:57] <Geth> ¦ rakudo/main: Previously Format.new read the @*DIRECTIVES dynamic after calling

[18:57] <Geth> ¦ rakudo/main: Formatter.new, but that dynamic only ever existed inside

[18:57] <Geth> ¦ rakudo/main: Formatter.AST, so the attribute always received a Failure. That broke

[18:57] <Geth> ¦ rakudo/main: Format.directives, and constructing a Format during a compilation

[18:57] <Geth> ¦ rakudo/main: made the instance unserializable: the Failure backtrace references

[18:57] <Geth> ¦ rakudo/main: <…commit message has 7 more lines…>

[18:57] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/2e49395508

[18:57] <Geth> ¦ rakudo/main: 2ed2d94c17 | (Nick Logan)++ | 3 files

[18:58] <Geth> ¦ rakudo/main: RakuAST: build constant format string literals at compile time

[18:58] <Geth> ¦ rakudo/main: 

[18:58] <Geth> ¦ rakudo/main: A constant q:o literal previously emitted a runtime Format.new call,

[18:58] <Geth> ¦ rakudo/main: paying the Formatter parse and EVAL on first use in every process,

[18:58] <Geth> ¦ rakudo/main: with a comment disabling the compile-time construction because the

[18:58] <Geth> ¦ rakudo/main: resulting objects misbehaved. Two problems stood in its way: the

[18:58] <Geth> ¦ rakudo/main: Failure that Format.new bound as its directives made the instance

[18:58] <Geth> ¦ rakudo/main: <…commit message has 9 more lines…>

[18:58] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/2ed2d94c17

[18:58] <Geth> ¦ rakudo/main: 87da335a40 | (Nick Logan)++ (committed using GitHub Web editor) | 5 files

[18:58] <Geth> ¦ rakudo/main: Merge pull request #6447 from ugexe/ugexe/rakuast-format-literal-compile-time

[18:58] <Geth> ¦ rakudo/main: 

[18:58] <Geth> ¦ rakudo/main: RakuAST: build constant format string literals at compile time

[18:58] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/87da335a40

[18:59] <ugexe> tony will have to fix the cert :(

[18:59] <lizmat> pinged him on #raku-infra

[19:17] <Geth> ¦ rakudo: ugexe++ created pull request #6456: RakuAST: give a stash reference its stash as compile-time value

[19:17] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6456

[19:18] <[Coke]> sounds like it was fixed, based on infra chat

[19:34] *** japhb left
[19:35] *** japhb joined
[20:36] <lizmat> yeah: https://raku.land/zef:raku-community-modules/NativeHelpers::Blob/changes?v=0.1.13

[21:32] <Geth> ¦ rakudo: ugexe++ created pull request #6457: RakuAST: rewrite a square by the power operator to a multiply

[21:32] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6457

[21:39] <Geth> ¦ rakudo/main: 52331171d9 | (Nick Logan)++ (committed using GitHub Web editor) | 2 files

[21:39] <Geth> ¦ rakudo/main: RakuAST: give a stash reference its stash as compile-time value (#6456)

[21:39] <Geth> ¦ rakudo/main: 

[21:39] <Geth> ¦ rakudo/main: Previously a name with a trailing :: claimed the resolved package as

[21:39] <Geth> ¦ rakudo/main: its compile-time value, where evaluating the name produces the .WHO of

[21:39] <Geth> ¦ rakudo/main: that package. A consumer of the compile-time value then saw the wrong

[21:39] <Geth> ¦ rakudo/main: object: my constant S = Foo::Bar:: bound S to the package where the

[21:39] <Geth> ¦ rakudo/main: legacy frontend binds the stash, and a compile-time consumer like the

[21:39] <Geth> ¦ rakudo/main: <…commit message has 5 more lines…>

[21:39] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/52331171d9

[22:27] *** hurufu left
[22:28] <[Coke]> Having a announcement that just dumps the changelog seems less useful each release.

[22:29] <[Coke]> esp. since we have 202 commits so far for this release.

[22:33] <japhb> "A lot of stuff happened.  Whoo-boy, it sure was a lot."  :-P

[22:35] *** apogee_ntv left
[22:40] <ugexe> yeah i think something like "RakuAST: various bugfixes and optimizations towards parity with the legacy frontend" would cover most of it

[22:41] <ugexe> the specific bugfixes probably aren't relevant to most people since generally speaking no one is using rakuast yet

[22:41] <[Coke]> I will do that. I don't think the release announcement needs even the shas

[22:41] <ugexe> but people are probably interested in progress being made in rakuast, so a few line items outlining that is still good

[22:41] <[Coke]> The other sections we can call out the individual items.

[22:42] <ugexe> yeah

[22:42] <[Coke]> Yup.

[22:42] <[Coke]> Cool.

[22:46] <Geth> ¦ rakudo/main: 228e029c96 | (Will Coleda)++ | docs/release_guide.pod

[22:46] <Geth> ¦ rakudo/main: Add note about cleaning up release announcement

[22:46] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/228e029c96

[22:46] <[Coke]> releasable6: next

[22:46] <releasable6> [Coke], Next release in ≈7 days and ≈20 hours. There are no known blockers. 122 out of 202 commits logged

[22:46] <releasable6> [Coke], Details: https://gist.github.com/5deac54b80126d2efd3a5f04e2cabe28