9 Mar 2026
[Coke] yup, first try fine on new clone here too 15:43
timo packagers don't have that kind of trouble, as they are supposed to take release tarballs anyway :) 16:40
[Coke] :) 16:44
Geth rakudo/main: a77416b8d8 | (Elizabeth Mattijsen)++ | src/core.c/IO/Path.rakumod
Simplify IO::Path.slurp

The optimizations into separate candidates were from a different era. Instead, handle all in a single candidate, to make it easier to add features later
18:49
rakudo/lizmat-translate-nl: 4c9141afb5 | (Elizabeth Mattijsen)++ | src/core.c/IO/Path.rakumod
Add :translate-nl named arg to IO::Path.slurp

Defaults to True. So specify :!translate-nl if you don't want newline
  (\r\n -> \n) translation. Slurping a file without newline translation
  *can* make it up to 7% faster.
As suggested in:
   github.com/rakudo/rakudo/issues/33...-569957370
19:01
rakudo: lizmat++ created pull request #6079:
Add :translate-nl named arg to IO::Path.slurp
10 Mar 2026
rakudo/main: eef0e946cf | (Elizabeth Mattijsen)++ | src/Raku/ast/variable-declaration.rakumod
RakuAST: the default scope of constants is 'my'

Not our. Reported by finanalyst++ in:
   github.com/Raku/problem-solving/issues/514
10:27
rakudo/main: 5cf4368e97 | (Elizabeth Mattijsen)++ | src/Raku/ast/variable-declaration.rakumod
Revert "RakuAST: the default scope of constants is 'my'"

This change was a bit premature, and needs a resolution to problem solving issue github.com/Raku/problem-solving/issues/514
This will then also need revision gating logic
11:11
lizmat TIL that "our" variables also create a MY:: entry 11:13
librasteve i'm sure there's a good reason for that 11:24
;-)
lizmat yeah, makes sense, quicker lookups and lowering 11:25
librasteve starts work on the weekly (a day late, hopefully not a dollar short) 11:26
lizmat ++librasteve 11:30
Geth rakudo/main: 7fc93d521c | (Elizabeth Mattijsen)++ | 7 files
Make all core constants "my" scoped

Better to be explicit!
12:18
rakudo/lizmat-my-constant: 25f3f36897 | (Elizabeth Mattijsen)++ | 4 files
Make default scope for "constant" "my" in 6.e

In response to github.com/Raku/problem-solving/issues/514
Handles both the legacy grammar as well as the new Raku grammar.
  - adds a "default-scope" attribute to VarDeclaration::Constant
  - make the default for that "my"
  - adapts the "default-scope" method to return that attribute
  - checks language revision to apply "my" or "our" as default scope
  - make sure that "default-scope" is specified in .raku
12:35
rakudo: lizmat++ created pull request #6080:
Make default scope for "constant" "my" in 6.e
rakudo/main: fffdb91fc6 | (David Schultz)++ (committed using GitHub Web editor) | src/core.c/Cool.rakumod
In methods of `Cool` that call methods of `Str`, coerce `Cool` parameters to the adequate types (#6021)

Str.contains() requires the second positional to be an Int. So one needs to convert the Cool $pos to Int, just as in the three multis above. This should fix the fact that Rakudo freezes when calling .contains with a Regex for $needle and non-Int Cool for $pos, e.g.: 12345.contains(/5/, "1") ... (9 more lines)
14:09
librasteve_ rakudoweekly.blog/2026/03/10/2026-...g-cragcli/ 14:50
Geth rakudo/main: ae4c136d8d | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/Repository/FileSystem.rakumod
Reduce a bit of work on -Ilib

The default extensions to look for don't need any post-processing. So only do post-processing if that is needed, and none if no extensions have been specified
16:56
rakudo/lizmat-no-pm-in-6e: 2cf8123865 | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/Repository/FileSystem.rakumod
Only look at .pm for code in 6.c/d with -I

Exclude the .pm extension if running in v6.e or higher in CURFS
17:11
rakudo: lizmat++ created pull request #6081:
Only look at .pm for code in 6.c/d with -I