|
🦋 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: fde5d87fe9 | (Stefan Seifert)++ | 3 files Fix iterating over Junction with non-simple loop bodies say .^name for any 1; should print "Junction" as we are iterating over a single Junction item. This already worked but only because of an optimization for loop bodies without any phasers or other complications. for any 1 { say .^name; LAST { } } printed "Int" indicating that the loop body got auto-threaded. That's because Junction objects don't ... (6 more lines) |
10:26 | |
| rakudo/main: 5cfa33aae1 | niner++ (committed using GitHub Web editor) | 3 files Merge pull request #5620 from rakudo/fix-looping-over-junction Fix iterating over Junction with non-simple loop bodies |
|||
|
14:41
evalable6 left,
evalable6 joined,
benchable6 left,
benchable6 joined
15:55
[Coke] left
15:56
[Coke] joined
|
|||
| Geth | roast: 371ce805ce | (Stefan Seifert)++ | S03-operators/assign.t Make %= test independent of the optimizer This test would fail when rakudo is run with --optimize=off as the broken usage of the operator does not throw an exception but instead stores a Failure. This Failure is stored in the variable. As it then is inside a container, p6sink won't call .sink on the Failure. The test worked as intended with the optimizer enabled, as we then generate a p6assign op which seems to have slightly different semantics. |
16:08 | |
rakudo/main: 7 commits pushed by (Stefan Seifert)++
|
16:54 | ||
| nine | That brings the count up to 1090 | ||
| sjn | really cool to see this kind of work done :-D | 16:58 | |
| nine | The whole exercise is really what I'd call "Learning Raku the hard way" | 17:02 | |
|
17:03
sena_kun left
17:05
sena_kun joined
|
|||
| Geth | rakudo/main: 87f150f71b | (Stefan Seifert)++ | src/Raku/Actions.nqp RakuAST: fix compilation of postfix ops on implicit $_ Fixes .++ as a shortcut for $_++ |
17:21 | |
| nine | That was an easy one | ||
| I hate it when tests depend on the optimizer | 17:30 | ||
| Geth | roast: b9b4770ed9 | (Stefan Seifert)++ | S03-operators/buf.t Fix tests depending on implementation details Whether the implementation of ~= uses the .Stringy method or the ~ prefix operator to stringify operands is an implementation detail and indeed even in current Rakudo depends on whether the optimizer is active, or not. We already check a very specific exception type. There shouldn't be a need to go beyond that. |
17:34 | |
| nine | That's 1092 then. | ||
|
18:21
sena_kun left
18:22
sena_kun joined
|
|||
| lizmat | 1091 for me | 18:57 | |
|
20:30
sena_kun left
20:41
finanalyst joined
20:51
finanalyst left
21:42
MasterDuke joined
22:53
tbrowder left
22:55
tbrowder joined
|
|||