🦋 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.
Geth rakudo/main: 5a0e7a7652 | (Elizabeth Mattijsen)++ | src/core.c/Any.pm6
Make List.Set work again without hanging

Works around github.com/rakudo/rakudo/issues/5229
10:25
Geth roast: 0d3c66572a | (Elizabeth Mattijsen)++ | 6 files
Add tests for Rakudo issue #5229
10:37
roast: b4a0d5bab4 | (Elizabeth Mattijsen)++ | 2 files
Add spectests for IterationBuffer
11:16
lizmat .ask jdv do you think you can find the time to do a 2023.03 release this month? 11:53
tellable6 lizmat, I'll pass your message to jdv 11:54
Geth rakudo/main: eae02e8ec5 | (Elizabeth Mattijsen)++ | src/core.c/Distro.pm6
Make Distr.desc correct for MacOS 11 and higher

Also add knowledge about Ventura.
13:31
Geth rakudo/main: e177bc2e3f | (Stefan Seifert)++ | 2 files
RakuAST: fix reporting of IllegalDecimal syntax error

Even though the parser already detected the illegal syntax and added a sorry for that, we still go on and try to create the AST which will be invalid, which causes an exception when trying to run BEGIN processing.
Catch this situation and avoid creating that invalid AST.
15:15
nine This ^^^ could have been just a one-line-change (replacing typed_sorry with typed_panic). Except, that it would break other tests in that file that expect 2 sorries for the same error. 15:33
My take away is, that our spec tests for parser errors are just too specific 15:34
lizmat I'd say, change the test to be less specific? 16:02
ugexe sorry sorry sorry 16:34
tonyo must be from michigan 16:35
lizmat that's close to Canada, right ? :-) 16:36
tonyo it is yea
patrickb o/ 19:21
Any reason not to merge github.com/rakudo/rakudo/pull/5211 ?
nine LGTM 21:37
Geth rakudo/main: 6e2a46f6c4 | (Jonathan Worthington)++ (committed by Patrick Böker) | src/core.c/Supply-coercers.pm6
Switch Supply.zip to a watermark approach

In github.com/Raku/problem-solving/issues/364 a proposed solution to a deadlock in supply setup is hindered by the failure of a spectest for Supply.zip.
Thus far we defined Supply.zip as having its reuslt Supply be `done` as ... (13 more lines)
21:48
rakudo/main: 2225e2079d | (Patrick Böker)++ | src/core.c/Supply-coercers.pm6
Fix Supply.zip watermark changes

We are only done when all supplies hit the watermark, not when the first hits the mark.
rakudo/main: 97e8523a23 | (Patrick Böker)++ (committed using GitHub Web editor) | src/core.c/Supply-coercers.pm6
Merge pull request #5211 from patrickbkr/watermarky-supply-zip2

Switch Supply.zip to a watermark approach (rework)