00:02 librasteve_ left
Geth rakudo: ugexe++ created pull request #6273:
RakuAST: don't drop a declaration when collapsing a constant conditional		 00:36
rakudo: ugexe++ created pull request #6274:
Accept a Mu lhs and rhs in the test-assign metaops		 01:10
rakudo: ugexe++ created pull request #6275:
RakuAST: route smartmatch through the smartmatch dispatcher		 02:35
rakudo: ugexe++ created pull request #6276:
RakuAST: don't run a parameter type's ACCEPTS when checking multi signatures
rakudo: ugexe++ created pull request #6277:
RakuAST: don't redeclare a special variable bound in a sub signature		 03:59
05:01 hurufu joined 05:38 finanalyst__ joined, finanalyst_ left 09:33 Guest55 joined 10:12 hurufu left 10:18 hurufu joined
[Coke] makes a very laggy connectin to IRC from mid-air. 11:20
lizmat
.oO( 8 miles high... :-)
 11:21
[Coke] hurls github.com/rakudo/rakudo/issues/6278 11:24
5 different commits to look at.
lizmat the App::RaCoCo is interesting, as it references a doc change :-)
[Coke] one of them is mine! 11:25
11:25 guifa_ joined
[Coke] note that the doc one also includes one exception text change. 11:25
yup. they are checking the text of the message, not the type 11:26
bug in module, should always prefer exception type if available. 11:27
lizmat yup
11:27 guifa left
[Coke] .seen atroxaper 11:27
tellable6 [Coke], I saw atroxaper 2023-01-16T03:08:56Z in #raku: <atroxaper> rf Voldenet: Thank you :)
lizmat the "vars" also looks like it is an iffy test
[Coke] I'll submit a PR for that one. 11:28
lizmat ack
++[Coke]
[Coke] (the pre-compile one)
Ah, pre-compile is coming from the stderr of another process. will update the regex instead. :| 11:32
11:33 Guest55 left
lizmat bisectable6: old=2026.05 CATCH { .resume }; "foo".EVAL 11:35
bisectable6 lizmat, Bisecting by output (old=2026.05 new=9b162bc) because on both starting points the exit code is 1
lizmat, bisect log: gist.github.com/62965646d4ebebbba8...cfb264a6c9
lizmat, (2026-06-10) github.com/rakudo/rakudo/commit/25...ebfb8f8ce8
lizmat the "vars" one is fixable 11:38
in the module
will do that later today
[Coke] PR submitted on racoco 11:42
I will be away next weekend, but should be able to kick off a second blin run (several commits to still process) 11:43
lizmat cool! 11:48
[Coke] ugexe: looks like ASTQuery is testing what the resulting AST nodes look like, and then fails a test because the optimization happened. 11:52
bug in the test 11:53
.seen fco 11:59
tellable6 [Coke], I haven't seen fco around, did you mean cog?
lizmat .seen Smokemachine
[Coke] -> afk
tellable6 lizmat, I saw Smokemachine 2026-06-04T01:26:50Z in #raku: <SmokeMachine> japhb: yes, thatā€™s Selkie::UIā€¦
lizmat [Coke] ^^
SmokeMachine FCO here! What have I done wrong? 12:00
lizmat ASTQuery needs its tests adapted because there are some simple optimizations in RakuAST now 12:01
SmokeMachine Iā€™ll try to take a look at it after work
lizmat ++SmokeMachine
github.com/rakudo/rakudo/issues/6278 12:02
14:03 librasteve_ joined
disbot4 <librasteve> please do help us to raise Raku awareness by going here news.ycombinator.com/item?id=48541940 in the next few minutes and commenting your thoughts (the metric is comments per minute) 14:38
15:22 hurufu left, hurufu1 joined 15:24 hurufu1 is now known as hurufu
SmokeMachine how can I see the error? I tried building raku main and run the tests, but no errors... 16:13
[Coke], lizmat ā˜ļø? 16:14
[Coke] are you including 801a103 16:15
that gives me the error here. 16:16
SmokeMachine I'm trying to `rakubrew build moar 801a103` and try again 16:17
[Coke] I tried it with 2026.05, worked fine, and moar-e93a9dfac1, and it failed. 16:18
(and the bisect took it to 801a103) 16:19
depending on why those tests, might want to match the optimized version, or (can we?) disable the optimizer to get original results, etc. 16:20
SmokeMachine www.irccloud.com/pastebin/NY7pHgAU/
I'm trying with moar-e93a9dfac1 16:21
[Coke] are you testing the published version? 16:26
or HEAD?
try "zef look ASTQuery" and when that opens "zef test ."
SmokeMachine I think mi6 is not using the right raku version... 16:27
[Coke] yah, I get the same error in your HEAD with 'zef test .'
did you install mi6 under this version of raku in rakubrew? 16:28
what does `which mi6` say? 16:29
SmokeMachine www.irccloud.com/pastebin/1nvTSKTY/ 16:34
I have another raku installed here... that was the problem... I'm trying to fix the test now 16:35
[Coke] \o/ 16:37
ugexe i wonder if an .AST(:optimize<off>) would make sense. someone would have to put some thought into it 16:45
SmokeMachine I think that's breaking the usability of the module... :( 17:14
lizmat wasn't this just about the test expecting the wrong thing ?
SmokeMachine no, it was expecting the correct thing before, but now it's not. For example `say 1 + 2`, it now is equivalent to `say 3`... I really think the AST should be related to what is written, and any optimizationshould come in a future step... 17:19
lizmat well, the future step is here :-)
SmokeMachine I mean future step of the compiler... 17:20
www.irccloud.com/pastebin/rzROGqT4/
librasteve_ rakudoweekly.blog/2026/06/15/2026-...oundation/ 17:22
lizmat librasteve_++
SmokeMachine if the AST is going to "be different from the code", that module kinda looses its value, no? 17:24
I don't really know what to do... :( 17:28
ugexe disable optimizations for your test? 17:30
i don't see how to have a separate optimization stage without serializing the resolver to pass between stages, which is something that needs to be done 17:31
SmokeMachine but that would work only for the tests... the usage would still be kinda blah...
ugexe "something that needs to be done" = avoiding serializing the resolver 17:32
SmokeMachine how do I disable optimizations for the test?
[Coke] I'm not sure what the purpose of those ASTQuery tests are - seems like if we want the AST to be a certain way for certain code, that's a rakudo test, not a a module test (and it's an internal detail we can change)
SmokeMachine the other option would be removing the module from the ecosystem, right? (and I'm not sure if that's an option...) 17:33
ugexe it can be removed from something Blin scans at least 17:34
[Coke] There is no way currently to remove a module. I think the suggested option is to release a version that then refuses to install, maybe.
(blin) right, that's easy
SmokeMachine [Coke]: I'm not saying it affects the purpose of the tests, but the purpose of the module itself.
[Coke] I mean, for now, I'm not considering this a blocker for the release.
SmokeMachine: I only looked at the test, one sec.
I mean, you can still match against the AST... 17:35
it's just that the AST may be simpler than expected.
ugexe would the theoretical .AST(:optimize<off>) or whatever be sufficient?
SmokeMachine I'm going to change the tests, but the module now is much less useful than it was before... 17:36
not simpler, different, the example `say 1 + 2`, search for `2` will never work... 17:37
ugexe: I suppose so 17:39
but it would not make sense to use the module if it would make your code slower... 17:40
[Coke] I think being able to dump/search the AST is helpful - the problem is expecting it to be a 1:1 to the code. I would "just" add caveats that because of the optimizer, you may find that some nodes you might expect will be skipped by the compiler. 17:45
ugexe well, it wouldnt be any slower than it currently is 17:46
[Coke] wonder if the optimizer could optimize slightly more of 'my $a =3; say $a-1+2*5-123'
(it reduces it to $a-1+10-123) 17:47
[Coke] puts a pin in that to look at maybe on the plane on the way back
ugexe ((($a - 1) + (2*5)) - 123) 17:50
there is probably a subset of $a that it could be optimized more 17:52
[Coke] yah, -1+2*5-123+$a collapses everything 17:57
ugexe m: my Num ($a, $b, $c) = 1e0, 1e20, -1e20; say ($a + $b) + $c == $a + ($b + $c);
camelia False
ugexe so we have to know the associativity for $a type's various operators 17:59
probably why the legacy frontend does optimize it either 18:00
doesnt^
SmokeMachine I just release a new version that the tests should be passing... 18:10

Powered by Cro and the RakuĀ® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!