[01:22] <ugexe> m: run $*EXECUTABLE, q|-e|, q|=begin end|; BEGIN %*ENV<RAKUDO_RAKUAST>=1

[01:22] <camelia> rakudo-moar c9d0f81cc: OUTPUT: «===SORRY!=== Error while compiling -e␤=begin may not be followed by directive 'end'␤at -e:1␤------> <BOL><HERE>=begin end␤The spawned command '/home/camelia/rakudo-m-inst-1/bin/perl6-m' exited unsuccessfully (exit code: 1, signal: 0)␤  in bl…»

[01:24] <ugexe> oh that module is really old

[01:24] <ugexe> BioPerl6

[01:42] *** MasterDuke joined
[01:43] <MasterDuke> am i remembering correctly? i thought `$foo.DUMP` was how you debug-printed something in RakuAST?

[02:41] *** MasterDuke left
[05:58] <lizmat> say $foo ?

[07:20] *** [Tux] left
[07:24] *** [Tux] joined
[09:22] *** finanalyst joined
[10:29] <Geth> ¦ rakudo/lizmat-23: 560ee4ca96 | (Elizabeth Mattijsen)++ | src/core.c/RakuAST/Fixups.rakumod

[10:29] <Geth> ¦ rakudo/lizmat-23: RakuAST: add Node.SOURCE method

[10:29] <Geth> ¦ rakudo/lizmat-23: 

[10:29] <Geth> ¦ rakudo/lizmat-23: This is mostly intended as a debugging aid.  If a RakuAST tree is

[10:29] <Geth> ¦ rakudo/lizmat-23: built from the Raku grammar, then you can call this method on any

[10:29] <Geth> ¦ rakudo/lizmat-23: RakuAST::Node object in the tree to obtain the source-code that

[10:29] <Geth> ¦ rakudo/lizmat-23: generated it.

[10:29] <Geth> ¦ rakudo/lizmat-23: 

[10:29] <Geth> ¦ rakudo/lizmat-23: This is similar in result as .DEPARSE, however the .SOURCE method

[10:29] <Geth> ¦ rakudo/lizmat-23: will just produce the source verbatim, inclusing any inline comments.

[10:29] <Geth> ¦ rakudo/lizmat-23: 

[10:29] <Geth> ¦ rakudo/lizmat-23: If a tree is synthetically built, then it will return Nil.

[10:29] <Geth> ¦ rakudo/lizmat-23: review: https://github.com/rakudo/rakudo/commit/560ee4ca96

[10:29] <Geth> ¦ rakudo: lizmat++ created pull request #6303: RakuAST: add Node.SOURCE method

[10:29] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6303

[10:35] *** donaldh joined
[11:00] <releasable6> Next release in ≈3 days and ≈7 hours. 1 blocker. Please log your changes in the ChangeLog: https://github.com/rakudo/rakudo/wiki/ChangeLog-Draft

[11:08] <patrickb> sub MAIN('a', :$what-is-this) { my $s = Set.new() (-) set('hi'); dd $s; }

[11:08] <patrickb> This outputs: $s = Set.new("what-is-this")

[11:08] <patrickb> lizmat: Is this down your alley?

[11:36] <lizmat> yes, and it has been fixed in HEAD

[12:09] <patrickb> Oh wow! Thanks!

[12:42] *** finanalyst left
[12:55] <[Coke]> Looks like "Facter" is hanging on tests.

[13:00] <[Coke]> blin tested through everything, only Facter was left, but had to kill the running, so I didn't get failures.md at the end.

[13:00] <[Coke]> output_App::RaCoCo_2.0.1  output_Needle::Compile_0.0.11          overview

[13:00] <[Coke]> output_MCP_0.33.6         output_Text::Markdown::Discount_0.3.0

[13:00] <[Coke]> Those were the 4 failures.

[13:12] <[Coke]> Put full result files here: https://github.com/coke/raku-blin-release-results/tree/2026.06.02

[13:13] <[Coke]> note that because we lost the failures.md we don't have the bisected commit, sorry

[13:13] <[Coke]> racoco was already patched.

[13:13] <[Coke]> well, a PR was submitted

[13:15] <[Coke]> I can't find a "not ok" in the output of MCP or Text::Markdown, and Needle is lizmat's.

[13:25] <ugexe> needle::compile needs its test changed: https://gist.github.com/ugexe/1e9b440aa3e4cb83968b14a27b2bfdec

[13:26] <ugexe> it was relying on the buggy behavior described in https://github.com/rakudo/rakudo/issues/5762

[13:33] <ugexe> i dunno why app::racoco... its a test that does a bunch of precomp stuff which makes me think it probably is doing something it shouldnt