🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
01:32 japhb left 01:35 japhb joined 02:01 nine left 02:02 nine joined 06:39 kjp_ left 06:55 kjp joined
lizmat Files=1352, Tests=117129, 305 wallclock secs (36.37 usr 9.77 sys + 4209.73 cusr 338.54 csys = 4594.41 CPU) 07:37
MasterDuke 305 is slower than usual, right? 08:21
09:00 MitarashiDango[m left
lizmat yes, but for now I think it's a fluke. We'll know tomorrow 09:16
I run these unattended at night when my computer is cold and not doing anything else (apart from backups, and that may have interfered)
09:42 ggoebel left
Geth rakudo: 5dd82a62d5 | (Elizabeth Mattijsen)++ | src/Perl6/ModuleLoader.nqp
Protect setting loading with a lock

There is at least a potential race on the %settings_loaded hash, and who knows inside of that block of code. Sadly, not enough to fix #1920, but it seems to now succeed more often, or *hang* more often.
10:41 [Tux] left 10:57 [Tux] joined 11:02 ggoebel joined 11:22 ggoebel left 11:31 ggoebel joined
Geth rakudo: 07d3030a78 | (Elizabeth Mattijsen)++ | src/Perl6/ModuleLoader.nqp
Make sure we release the lock on exception

  jnthn++ for the nudge
12:13 ggoebel left 12:55 ggoebel joined
lizmat meh, looks like we lost bisectable6 ? AlexDaniel ?? 13:26
.seen bisectable6 13:27
Geth rakudo/treat-unequal-special: 0d8052572d | (Elizabeth Mattijsen)++ | src/Perl6/Actions.nqp
Treat <<!=>> special

In response to github.com/rakudo/rakudo/issues/4838
The applied fix feels hacky, but != *is* the only op that is actually implemented as an op, and not as meta-handling applied to an op. Suggestions for better fix welcome!
rakudo: lizmat++ created pull request #4839:
Treat <<!=>> special
15:02 discord-raku-bot left 15:03 discord-raku-bot joined
Geth rakudo: bf50105f80 | (Elizabeth Mattijsen)++ | 7 files
Trailing whitespace spring-cleaning
roast: ed50f3c48d | (Elizabeth Mattijsen)++ | 206 files
Trailing whitespace spring-cleaning
rakudo: 540c73655c | (Jonathan Worthington)++ | src/core.c/Match.pm6
Relax `make`'s type check on `$/`

It seems that Inline::Perl5 uses the Raku `make` on an NQPMatch, and that - due to a dubious optimization - that actually works out. For now, relax it to permit NQP match objects too, so we can keep the improved error without regressing Inline::Perl5.
AlexDaniel I'm here, I'll check 15:43
Ok that was kinda expected 15:44
15:44 committable6 joined, bisectable6 joined, sourceable6 joined, bisectable6 left 15:45 quotable6 joined
AlexDaniel commit: help 15:45
committable6 AlexDaniel, Like this: committable6: f583f22,HEAD say ‘hello’; say ‘world’ # See wiki for more examples: github.com/Raku/whateverable/wiki/Committable
AlexDaniel Should be back up soon
15:45 coverable6 joined, linkable6 joined 15:46 notable6 joined, nativecallable6 joined, releasable6 joined, bloatable6 joined 15:47 reportable6 joined, bisectable6 joined
AlexDaniel bisect: help 15:49
bisectable6 AlexDaniel, Like this: bisectable6: old=2015.12 new=HEAD exit 1 if (^∞).grep({ last })[5] // 0 == 4 # See wiki for more examples: github.com/Raku/whateverable/wiki/Bisectable
AlexDaniel lizmat: please check. Fixing tellable is still my weekend project though 15:50
lizmat AlexDaniel++ 15:51
bisectable6: say @a «!=» @a;
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, Sorry kid, that's not my department.
lizmat, Bisecting by output (old=2022.03 new=540c736) because on both starting points the exit code is 1
AlexDaniel Damn 15:52
:-/ ok sry will need to fix that too
That feels like something is wrong with it's GitHub access 15:53
Its*, come on autocorrect :D
lizmat no worries: I actually have a PR for that code, but was just curious if it was a regression at some point 15:54
Geth rakudo/rakuast: 454 commits pushed by (Jonathan Worthington)++, (Moritz Lenz)++, (Elizabeth Mattijsen)++, (Timo Paulssen)++, (Brad Gilbert)++, (Daniel Green)++
review: github.com/rakudo/rakudo/compare/b...d039c84b41
rakudo: f3b1e95d05 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/Perl6/Actions.nqp
Treat <<!=>> special (#4839)

In response to github.com/rakudo/rakudo/issues/4838
The applied fix feels hacky, but != *is* the only op that is actually implemented as an op, and not as meta-handling applied to an op. Suggestions for better fix welcome!
rakudo/rakuast: 5c6f961ecc | (Jonathan Worthington)++ | src/Raku/Grammar.nqp
Add $*BORG bits for missing block

So we get missing block errors rather than an error about calling missing block with the wrong number of arguments.
16:11 linkable6 left 16:14 linkable6 joined
Geth roast: fc80cf6b3a | (Elizabeth Mattijsen)++ | S03-metaops/hyper.t
Add test for #4838
rakudo/rakuast: 3c008bb3a2 | (Jonathan Worthington)++ | src/Raku/Grammar.nqp
Attach position information to parse errors

So far, the RakuAST-based compiler hasn't been reporting the location of syntax errors. The way this is factored in the current compiler mixes the concerns of assembling the exception object with extracting various bits and pieces that it's the parser's job to know about. In RakuAST we need something a bit cleaner, and less coupled to any particular parser. ... (7 more lines)
rakudo/rakuast: 5a0aae5edc | (Jonathan Worthington)++ | src/Raku/Grammar.nqp
Parse multiline comments in RakuAST-based compiler
rakudo: 556855720b | (Elizabeth Mattijsen)++ | src/Perl6/Actions.nqp
Make Actions.wanted us some more temporary variables

Rather than keeping calling methods again and again. Shaves off about .3 seconds from building the 6.c setting (out of ~50 seconds) It's not a lot, but it was an easy gain that is applicable to *all* parsing / precompilation (about .6%).
18:16 reportable6 left 18:17 reportable6 joined
Geth rakudo: 397145a612 | (Elizabeth Mattijsen)++ | src/Perl6/Actions.nqp
Make Actions.unwanted use some more temporary variables

Rinse and repeat from 556855720b
18:20 casaca joined
Geth rakudo/show-WHY: d61b4d2beb | (Elizabeth Mattijsen)++ | src/core.c/Exception.pm6
Improve typecheck errors on e.g. subsets

Check whether there's a WHY on the expected value, and show the WHY if there is one in the message. Example:
   #| Only "foo" is acceptable!
   subset Foo of Str where $_ eq "foo";
... (5 more lines)
rakudo: lizmat++ created pull request #4840:
Improve typecheck errors on e.g. subsets
lizmat that concludes my hacking for today& 19:33
20:00 statisfiable6 joined 20:01 bisectable6 left 20:02 bisectable6 joined 20:03 benchable6 joined, squashable6 joined 20:04 unicodable6 joined, evalable6 joined, evalable6 left, benchable6 left, bisectable6 left, squashable6 left, statisfiable6 left, releasable6 left, linkable6 left, coverable6 left, quotable6 left, bloatable6 left, notable6 left, unicodable6 left, sourceable6 left, nativecallable6 left, reportable6 left, committable6 left, linkable6 joined, sourceable6 joined, squashable6 joined, greppable6 joined 20:05 reportable6 joined, statisfiable6 joined, shareable6 joined, notable6 joined, coverable6 joined, evalable6 joined 20:06 committable6 joined, unicodable6 joined, nativecallable6 joined, squashable6 left 20:07 quotable6 joined, bloatable6 joined, benchable6 joined, bisectable6 joined, releasable6 joined
patrickb [Coke], jdv: Did you notice my questions in github.com/rakudo/rakudo.org/pull/78 ? 20:07
AlexDaniel bisectable6: say @a «!=» @a; 20:09
bisectable6 AlexDaniel, Will bisect the whole range automagically because no endpoints were provided, hang tight
AlexDaniel, Output on all releases: gist.github.com/0e842b28f43f7298cf...fc7ca8535c 20:10
AlexDaniel, Bisecting by output (old=2022.03 new=397145a) because on both starting points the exit code is 1
AlexDaniel, bisect log: gist.github.com/90baae527b17a619c4...8bc2a0a732
AlexDaniel, (2022-03-23) github.com/rakudo/rakudo/commit/a5...ce933274f0
AlexDaniel, Output on all releases and bisected commits: gist.github.com/9682e4bdb55230f6df...ee5809af3c
AlexDaniel lizmat: ok, it works now... It was a precomp issue
I kinda remember it, if you update a lib you have to remove precomp files 20:11
That sounds wrong of course, but it gets complicated because bots actually are not allowed to write anything 20:12
So they can't update the precomp files if anything changed
Therefore all these weird bugs
Fixed by removing precomp files, then letting then write them, and then restarting again 20:13
22:38 discord-raku-bot left, discord-raku-bot joined, gfldex left 22:41 gfldex joined 22:44 discord-raku-bot left 22:45 discord-raku-bot joined