🦋 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.
08:12 sena_kun joined
Geth nqp/main: 1ec7ed3fd6 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION
Bump MoarVM with lazy deserialization fix

rakudo/main: d6320eaff9 | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
Bump NQP to get laze deserialization fix
lizmat REA harvester now running with fix, keeping fingers crossed! 09:30
nine lizmat: there's something odd in the IRC logs: irclogs.raku.org/raku-dev/2024-04-10.html#07:46 that line with "BUT" should be 3 lines below 10:04
lizmat seems to match the raw log: irclogs.raku.org/raku-dev/2024-04-10.log 10:06
so it's not a rendering issue 10:07
Geth rakudo/main: 312a5d857b | (Stefan Seifert)++ | 2 files
RakuAST: support arguments on require statements
rakudo/main: 9ca35fb965 | (Stefan Seifert)++ | 7 files
RakuAST: Fix required symbols not getting used

For Foo::Bar.foo we currently generate code like QAST::Op.new(:op<callmethod>,
  :name<foo>, QAST::WVal.new(:value(Foo::Bar)). Works beautifully because we
have a compile-time-value for Foo::Bar which either comes from the setting, got imported via use (a BEGIN time effect) or is something we just compiled ourselves. ... (15 more lines)
lizmat nine: so that'd be 100% of the way now? :-) 10:15
nine Let's hope so :) 10:19
lizmat cool! 10:20
REA is running every 10 minutes now, no crashes yet
Geth rakudo/main: 698836830d | (Stefan Seifert)++ | src/Raku/ast/expressions.rakumod
RakuAST: support colon pairs on dotty infixes

Fixes my Pair $p .= new :key<k>, :value<v>
lizmat 1029! 10:45
nine: oddly enough, I got some new failures on "make test", can you confirm?
this could be from any commit in the past days, didn't run any RakuAST tests for a while 10:46
nine Like....all of NativeCall again
lizmat yeah :-( 10:50
ok, so it was not just me :-(
No such method 'is-resolved' for invocant of type
seems an easy fix? 10:51
nine probably
Wth the NativeCall tests segfault 10:56
Ok, that may be some precomp screwup. Cleaning those helped with the segfault 11:00
lizmat *phew* 11:09
11:13 evalable6 left 11:18 evalable6 joined
Geth rakudo/main: e52a456f06 | (Stefan Seifert)++ | src/Raku/ast/statements.rakumod
RakuAST: fix regression in require

Fixes "No such method 'is-resolved' for invocant of type
  'RakuAST::Declaration::Import'". No idea how this could slip through.
  lizmat++ for spotting
rakudo/main: 09abf8206c | (Stefan Seifert)++ | src/Raku/Actions.nqp
RakuAST: support the other indirect method call syntax

Implements support for e.g. key($pair:)
nine 1031 11:49
Oh, we don't support macros at all yet 11:50
lizmat and 140 for "make test" :-) 11:52
11:54 sena_kun left
Geth rakudo/main: 3a836f23b0 | (Stefan Seifert)++ | src/Raku/Grammar.nqp
RakuAST: bring back some more parse checks on calls
nine 1032
lizmat confirmed :-) 12:28
ab5tract I'll merge R#5549 in little bit, unless anyone has an objection 12:35
linkable6 R#5549 [open]: github.com/rakudo/rakudo/pull/5549 Add dispatch disambiguation via 'is item' parameter trait
lizmat has no objection 12:36
Geth rakudo/main: 5 commits pushed by ab5tract++ 14:27
14:47 [Coke] left, [Coke] joined
lizmat 30+ runs of the REA harvester, and no crash yet! :-) 15:06
ugexe wanna try the example 1 liner from github.com/rakudo/rakudo/issues/1920 ? 15:09
or just `raku -e 'await Promise.allof: (1..100).map({ start { require Test; } });'` a few times 15:10
that sometimes would give me an error mentioning `dependencies+deserialize` 15:11
lizmat yeah, still crashes, also in RakuAST 15:13
the REA crash produced a good backtrace though... one that didn't make sense. but an NQP backtrace still 15:14
15:58 MasterDuke left 17:37 sena_kun joined
nine lizmat: so REA's now fine? 18:58
lizmat nine: yeah, still ok after 50+ runs 18:59
before, it would have crashed 2..3 times already
nine That was great detective work of yours :) 19:08
lizmat yeah, bugged me for 6+ months :-)
in hindsight, I had a pretty good idea of what was going on (namely an nqp::create() without calling .new) 19:09
but I never found how that could happen, until I had an aha erlebnis :-) 19:10
19:19 MasterDuke joined 21:04 sena_kun left 21:05 sena_kun joined 23:29 sena_kun left