🦋 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 JSON-Unmarshal/main: 3bab708d59 | (Vadim Belman)++ | 2 files
Fixed another problem with nominalizables

When the nominal of a nominalizable is a non-supported class (none of Int, Str, etc. – like, say DateTime) we were failing to obtain attributes.
00:44
JSON-Unmarshal/main: e0c2237df3 | (Vadim Belman)++ | t/040-types.rakutest
Remove JSON::Class used for debugging purposes
00:49
JSON-Unmarshal/main: 2a67b3e23f | (Vadim Belman)++ | 2 files
0.10
Geth rakudo/rakuast_wip: f6df1a2258 | (Stefan Seifert)++ | src/Raku/ast/code.rakumod
Add a fallback resolver for BEGIN time run code objects.

Ye olde implementation created a wrapper frame containing the lexical symbols of all outer scopes. This is rather costly and blows up bytecode size. Instead, we now use the VMs new capability to run a custom resolver when it cannot find a lexical by itself.
This first implementation only gets us compile-time-known values, but it's a start.
08:45
rakudo/rakuast_wip: e77da5dfc8 | (Stefan Seifert)++ | src/Raku/ast/statementprefixes.rakumod
Fix BEGIN as statement prefix
[Tux] Rakudo v2022.06-46-g934f9895e (v6.d) on MoarVM 2022.06-6-gc315523ab
csv-ip5xs0.915 - 0.925
csv-ip5xs-205.599 - 5.631
csv-parser3.485 - 3.754
csv-test-xs-200.402 - 0.436
test6.803 - 7.048
test-t1.530 - 1.743
test-t --race1.138 - 1.191
test-t-2019.975 - 22.158
test-t-20 --race6.769 - 7.405
12:40
lizmat notable6: weekly 12:58
notable6 lizmat, 1 note: 2022-07-07T14:09:57Z <lizmat>: stackoverflow.blog/2022/07/06/why-...nt-3083485
lizmat notable6: weekly reset 12:59
notable6 lizmat, Moved existing notes to “weekly_2022-07-11T12:59:13Z”
lizmat And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2022/07/11/2022-...nciations/ 13:03
vrurg lizmat++ 14:38
Geth rakudo: vrurg++ created pull request #4981:
Fix a deep recursion issue in return typecheck dispatcher
20:14
rakudo/rakuast: 35b9789dc2 | (Stefan Seifert)++ | src/Raku/ast/statementprefixes.rakumod
Fix BEGIN as statement prefix
20:19
rakudo/rakuast: 0614d2e4db | (Stefan Seifert)++ | 2 files
Fix anonymous methods checking for wrong invocant type

Anonymous methods, i.e. method () { ... } created inside another method's body checked their invocant against the outer method's package. This broke method foo() { Proxy.new: FETCH => method () { ... } ... }
Fix by only generating code for checking an implicit invocant's type on named methods.
timo i wonder if we need to wargame the kinds of situation happening to other package ecosystems and infrastructures over the last years 21:28
like, can we put something on the ipfs that could be used as a fail-safe? signed by a trusted key to give installations of raku that can't easily be maintained in the case of a sudden catastrophical loss of raku packaging infrastructure 21:32
japhb timo: Well, we still have a tendency towards radical trust, which has served us well over the decades, but ... yeah, suboptimal now.
timo at some point someone will come and prove to us that trusting is foolish :ed 21:33
:D
timo how well does udp broadcast tend to work in l 21:42
cloud infrastructures
can we just put avahi into our package manager
Geth rakudo: 9fa76ec642 | (Vadim Belman)++ | src/vm/moar/dispatchers.nqp
Fix a deep recursion issue in return typecheck dispatcher

Should have used `wrapee-lookup` on SubsetHOW itself.
23:31
rakudo: 808b07682a | (Vadim Belman)++ | src/vm/moar/dispatchers.nqp
Use slightly faster nqp::how_nd where possible

Where we can guarantee that no container would slip in.
rakudo: e7acf4930a | (Vadim Belman)++ (committed using GitHub Web editor) | src/vm/moar/dispatchers.nqp
Merge pull request #4981 from vrurg/rakudo-4980

Fix a deep recursion issue in return typecheck dispatcher