🦋 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:19 MasterDuke joined 02:03 vrurg_ left 02:04 vrurg joined 04:09 MasterDuke left 05:42 vrurg left, vrurg joined
nine The whole language version management code is absurdely complex. We have - including all subvariants - just 7 different language versions. How can this require 200 lines of code including generated code? 07:16
07:55 sena_kun joined
Geth rakudo/main: c053144ab5 | (Stefan Seifert)++ | src/Raku/Actions.nqp
RakuAST: fix regression on `use v6.*;`

On a use v6.* $vWant turned out to be "v*". But we can just use
  @final-version instead. The first part will be the revision number.
  lizmat++ for the heads-up
08:05
ab5tract considering that language versions are not totally clean breaks between each other (v6.d has many more features/fixes now than when released), I wonder if it's worth revisting nemokosch's critiques of the release strategy/versioning scheme now that said discussion is less liable to be soaked in vitriol 09:09
09:15 sena_kun left
nine m: sub foo($a is copy) { BEGIN dd $a; dd $a; $a := Mu }; foo(1) 10:23
camelia Mu
Any $a = 1
Type check failed in binding; expected Any but got Mu (Mu)
in sub foo at <tmp> line 1
in block <unit> at <tmp> line 1
nine Is it really desired behavior that at compile time the parameter $a has a value of Mu instead of Any? 10:24
lizmat I think it's more an implementation artefact than anything else 10:36
as Mu is the base state in HLL Raku? 10:37
10:38 finanalyst joined
nine t/02-rakudo/13-exceptions.t tests specifically for Mu in that error message 10:43
lizmat I'd say we adapt the test: it's an implementation detail, not in roast 10:45
11:14 sjn left
ab5tract I've been looking for a while but haven't found it yet.. how exactly would one go about peeking into the value held in a MVM (frame) register? 11:21
Comments in the source say that I need to use a temporary register to store any value that is going to be read, but that's as far as I've been able to get.. 11:25
11:53 finanalyst left
[Tux] Rakudo v2024.03-179-gc053144ab (v6.d) on MoarVM 2024.03-6-gd5dafa9b4
csv-ip5xs0.260 - 0.265
csv-ip5xs-201.124 - 1.140
csv-parser1.545 - 1.588
csv-test-xs-200.142 - 0.142
test1.926 - 2.016
test-t0.419 - 0.423
test-t --race0.272 - 0.272
test-t-205.100 - 5.134
test-t-20 --race1.198 - 1.235
13:03
nine ab5tract: in what environment? In gdb I just `p *tc->cur_frame->work[123].o` 13:13
MVM_dump_p6opaque is also quite helpful there 13:14
ab5tract Ah, I was hoping for something a bit more high level, like using debug statements from the QASTRegexCompilerMAST routines I’m poking at 13:22
I’ve added a workable print_debug method to MAST::Frame that’s guarded by an env var 13:24
13:41 sjn joined 13:59 Util left 14:11 lizmat_ joined 14:15 lizmat left 14:16 lizmat joined 14:17 lizmat__ joined 14:20 lizmat_ left 14:21 lizmat left, lizmat__ left, lizmat joined 15:13 lizmat_ joined 15:16 lizmat left
ab5tract I tried using the assign op, but so far that refuses to work on a variable. Maybe I can get further with bindattr 15:21
15:52 lizmat joined 15:55 lizmat_ left
ab5tract just tried poking at `./rakud-lldb-m` and .. this is definitely going to be a learning curve 17:41
18:01 sena_kun joined 18:30 sena_kun left, sena_kun joined 18:42 Altai-man joined, sena_kun left 19:11 sena_kun joined, Altai-man left 19:34 sena_kun left 19:35 sena_kun joined 19:58 finanalyst joined 20:53 sena_kun left, sena_kun joined 21:58 vrurg left 22:07 vrurg joined 22:35 lizmat_ joined 22:39 lizmat left 22:49 lizmat_ left, lizmat joined 23:11 sena_kun left