🦋 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: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
00:00 reportable6 left 00:01 sena_kun left 00:02 reportable6 joined
Geth rakudo/rakuast: 136 commits pushed by 17 authors
review: github.com/rakudo/rakudo/compare/3...031ec22499
rakudo/main: 92 commits pushed by (Stefan Seifert)++, (Vadim Belman)++
review: github.com/rakudo/rakudo/compare/5...031ec22499
vrurg [Coke]: are you around yet? 00:50
Turns out I cannot change the settings of Rakudo repository. Can't set the primary branch to main. 00:54
Geth rakudo/main: c3e0eb7c18 | (Vadim Belman)++ | 2 files
Make Azure pipelines know about the `main` branch

We are currently still stick to `master` in MoarVM and NQP repos. So, make sure the script still works with these too.
01:38 linkable6 left 01:40 linkable6 joined 01:42 Kaiepi left
Geth rakudo/main: ad9302d7a8 | (Vadim Belman)++ | tools/build/checkout-repos-for-test.pl
Fix a syntax error in Perl code

Well, too many year with Raku...
problem-solving: add472a844 | (Vadim Belman)++ | solutions/rakudo/Use-main-branch.md
Resolution for #298
problem-solving: e1a76d0ea0 | (Vadim Belman)++ (committed using GitHub Web editor) | solutions/rakudo/Use-main-branch.md
Merge pull request #356 from vrurg/issue_298

Resolution for issue 298
vrurg Just in case. I don't see a specific 'disable force pushes' in branch rules. But hope that 01:52
'Do not allow bypassing the above settings' makes this a default, considering a specific 'Allow force pushes' settings at the end. 01:53
[Coke] vrurg: hello 02:02
vrurg [Coke]: hi. :) Nevermind, all solved. I thought you have admin in Rakudo repo, but jnthn has fixed this for me already. 02:03
02:37 discord-raku-bot left, discord-raku-bot joined
[Coke] (y) 02:44
03:13 MasterDuke joined
Geth rakudo/main: 7194b1e6b3 | (Vadim Belman)++ | 2 files
Resolve the case of CUPR auto-vivifying some dynamics

First, make sure `$*CU` is not brought to life when not explicitly declared by a caller.
Second, as there is no way to avoid vivification of `$*EXECUTABLE` for precompiling the `Test` module, make sure we have the variable always, not only after the precompilation.
rakudo/main: c6afe38230 | (Vadim Belman)++ | t/02-rakudo/07-implementation-detail-6.c.t
Fix the list of expected symbols
rakudo/main: a5dd70affa | (Vadim Belman)++ | 2 files
Make sure not passwing RakuAST tests don't break our CI

Since RakuAST is not the mainstream yet it's ok to bypass the tests for now.
nqp: vrurg++ created pull request #788:
Adapt CI for the `main` branch
nqp/main: c68121a313 | (Vadim Belman)++ | 2 files
Adapt CI for the `main` branch

Change names and pick the checkout repos tool from Rakudo where it's been fixed already.
nqp/main: c8a811a008 | (Vadim Belman)++ (committed using GitHub Web editor) | 2 files
Merge pull request #788 from vrurg/main

Adapt CI for the `main` branch
04:13 evalable6 left, linkable6 left 04:15 linkable6 joined, evalable6 joined
MasterDuke vrurg: i assume you've noticed the fails in a spectest? looks like some of them might be related to the nqp backtrace work 04:39
oh, in t/spec/S03-operators/precedence.t it's actually a passing TODO. the fails are in t/spec/S32-exceptions/misc.t 04:40
06:00 reportable6 left 06:02 reportable6 joined 06:27 Kaiepi joined 08:10 evalable6 left, linkable6 left 08:11 evalable6 joined 08:13 linkable6 joined
Geth rakudo/✨-fail-push-to-master: 8ec871c832 | (JJ Merelo)++ | .github/workflows/dont-push-to-master.yml
Add workflows that fails if pushed to master
rakudo: JJ++ created pull request #5125:
Add workflows that fails if pushed to master
09:52 sena_kun joined 11:01 Kaiepi left
Geth roast: 0706b3fe60 | (Elizabeth Mattijsen)++ | S03-operators/precedence.t
Untodo now passing test
rakudo/main: dcbd66ce32 | (Elizabeth Mattijsen)++ | src/core.e/Formatter.pm6
Unbitrot Formatter

The RakuAST builder for sprintf
Nemokosch 🥳 11:21
11:35 discord-raku-bot left, discord-raku-bot joined 12:00 reportable6 left 12:01 reportable6 joined 12:46 Kaiepi joined
ugexe is rakubrew going to work with the changed branch names? 13:46
when i changed zefs primary branch it broke rakubrew
when i changed zefs primary branch it broke rakubrew 13:47
lizmat good question... 13:51
15:48 guifa left 15:49 guifa joined 16:14 sena_kun left 16:19 sena_kun joined
Geth rakudo/main: a174de25aa | (Elizabeth Mattijsen)++ | src/core.e/Formatter.pm6
Make Formatter more user friendly and efficient

  - replaced the cache by a lockless threadsafe version, so that each
   call to zprintf doesn't need a lock, at the expense of potentially
   more than one thread attempting to create the code for the same
... (21 more lines)
18:00 reportable6 left 18:02 reportable6 joined
Geth rakudo/main: 760b919891 | (Elizabeth Mattijsen)++ | src/core.e/Formatter.pm6
Fix some Formatter parsing issues

Found when running through the sprintf tests in roast
18:57 sena_kun left 19:00 sena_kun joined 20:00 evalable6 left, linkable6 left, linkable6 joined 20:01 evalable6 joined
vrurg MasterDuke: weird, it was passing on my side. 20:25
20:26 sena_kun left 20:40 squashable6 left, squashable6 joined 20:44 sena_kun joined 20:47 sena_kun left
Geth rakudo/main: b0f9d8324e | (Elizabeth Mattijsen)++ | src/core.e/Formatter.pm6
Fix issue with 0 precision and the value 0

Apparently, if the precision is 0 for an integer value format type, the value 0 should be rendered as an empty string, rather than as
  "0". This has been codified in roast that way
Nemokosch how can community modules be released? 23:11
vrurg MasterDuke: ok, got it. Of course it fails if you play with NQP from the main. ;) Now instead of incorporating the changes into Rakudo and teching Backtrace the new rules I lost time tracking down what could be wrong about the test, because mine NQP was the same! ;) 23:13