🦋 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: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
Geth Pod-To-Man/main: 6 commits pushed by (Vadim Belman)++ 03:14
Pod-To-Man/main: ead0e99601 | (Vadim Belman)++ | t/01-basic.rakutest
Remove accidental Pod::To::HTML from the test
03:16
Pod-To-Man/main: 6e8b4b9138 | (Vadim Belman)++ | 2 files
0.2.0
03:19
[Tux] Rakudo v2022.04-87-g77bc03047 (v6.d) on MoarVM 2022.04-3-ga9fcd5a74
csv-ip5xs0.744 - 0.819
csv-ip5xs-205.028 - 5.217
csv-parser3.587 - 3.684
csv-test-xs-200.411 - 0.419
test6.167 - 6.339
test-t1.367 - 1.381
test-t --race0.815 - 0.820
test-t-2021.461 - 21.999
test-t-20 --race6.385 - 6.834
10:44
Xliff P6-GLib suite timing statistics for Raku 2022.04.87.g.77.bc.03047 12:01
Total number of projects: 32
Total non-parallel compile times: 8628.590 (269.643 avg)
Total parallel compile times: 1586.197 (49.569 avg) 5.440x speedup
jdv starting release 17:36
Geth rakudo/release-2022.06: 1b1e68fa7c | (Justin DeVuyst)++ | 3 files
Update changelog + announcement

Deliberately not logged:
  [add767e2][50025c1a][19c3bd18][a2601fbf][8140c55b][bfad9bd6][92ee0a74]
  [74a60a96][1f37c1c7][6bd19e40][f93aed0b][1c468054][214366a1][d09bde66]
  [b15394b6][ab8ef0bf][77bc0304]
19:17
nqp: 561a0b8da7 | (Justin DeVuyst)++ | tools/templates/MOAR_REVISION
[release] Bump MoarVM revision to 2022.06
20:17
nqp: 4400678ab9 | (Justin DeVuyst)++ | VERSION
[release] Bump VERSION to 2022.06
rakudo/release-2022.06: 2f9bb38d6d | (Justin DeVuyst)++ | tools/templates/NQP_REVISION
[release] Bump NQP revision to 2022.06
rakudo/release-2022.06: 6163fabcaa | (Justin DeVuyst)++ | VERSION
[release] Bump VERSION to 2022.06
jdv anyone know if github.com/rakudo/rakudo/blob/mast...kefile#L72 can be removed? 20:25
its been failing for a while so assuming its ok to dump 20:26
rba: ^? 20:28
Geth rakudo: jdv++ created pull request #4943:
Release 2022.06
20:49
rakudo/master: 4 commits pushed by (Justin DeVuyst)++ 20:51
jdv i believe the releasings are done for today 21:18
patrickb: 2022.06 release just happened 21:21
.tell El_Che 2022.06 release just happened
tellable6 jdv, I'll pass your message to El_Che
Xliff Does anyone know what this error means?
<Xliff> ===SORRY!=== Error while compiling /home/cbwood/Projects/p6-GtkPlus/lib/GTK/Box.pm6 (GTK::Box) 21:22
<Xliff> New type Stash for CompUnit::DependencySpecification is not a mixin type
vrurg Can you get a full stack trace?
--ll-exception, I mean.
Xliff Um.... One sec. 21:24
vrurg But in general it means that somewhere an attempt to rebless CUDS into Stash took place. 21:26
Xliff vrurg: Try here gist.github.com/Xliff/2f7216dae1dd...3de25d0e70
vrurg: Also gettng errors when installing Attrx::Mooish 21:29
vrurg BTW, what Rakudo release is it? Or is it master? 21:31
Xliff It's blead 21:32
AttrX::Mooish installs fine on 2022.03 21:33
vrurg Also installs on my master. 21:34
From the trace, it looks like a problem in MoarVM deserialization. 21:35
Xliff Another thing... "zef look NativeLibs" is putting me in the DBIish distribution 21:39
vrurg Xliff: do you, by occasion, use a BEGIN in the module?
Somehow it looks like we have a big issue with serialization. github.com/rakudo/rakudo/issues/4933 21:41
Xliff vrurg: Yes, plenty. 21:42
vrurg I don't have sufficient information to make conclusions, but it very much feels to me like either a context get lost, or just some kind of general mess up happens. 21:43
Xliff *sigh*
vrurg Xliff: then it is likely that the issue I mentioned above is being caused by the same bug.
Xliff Thewre are no BEGIN blocks in th at compunit. Might be one or two in the dependencies. 21:44
vrurg Xliff: that's about the scenario. In lizmat's case the error is triggered with BEGIN is a use'd module. 21:45
ggoebel_ jdv++ 22:00
Geth rakudo: vrurg++ created pull request #4944:
Fix cases where we try calling methods on BOOTCode
22:15
Xliff II have been having problems with this error, and it's finally pissed me off: 22:16
P6M Merging GLOBAL symbols failed: duplicate definition of symbol Container
Why is this merge having issues? It's keying on "Container" when it should be keyng off of its full name. 22:17
I am not even exporting the class, and it's still using the short name?
I don't even know how to golf it properly, although I will make a stab at it, shortly.
Can som,eone explain this issue to me? 22:18
vrurg Xliff: I don't remember all the details, but the problem is about nesting symbols, not about exports. For A::B::C::D D may result in duplication if in one place you get a module A::B::C, and another place ends up with a stub package A::B::C which has symbol D in it. 22:21
It's really not easy to golf down.
And it is not easy to get fixed until we are capable of single-process precomping. 22:22
Because the sub package can be produced by one compiling process, whereas the module is compiled by another, and third one tries to load merge it all. 22:23
I have the only workaround for this. For any delcared package A::B::C::D I have a `use A::B::C;` statement. In this case it is guaranteed that whenever symbols are merged they are merged into the same package object. 22:25
Xliff Um. Ouch. That workaround kinda depends on the fact that you can have an A::B::C 22:26
Thanks for letting me know about that, thougy. I may need to rearrange a lot of code. 22:27
vrurg Xliff: BTW, I've got lost a bit. With regard to AttrX::Mooish – would you, please, report the issue? Perhaps it's something I can get fixed. Also, make sure it's not trying to use v0.8.900 which is a development branch and was published by accident. :(
Xliff vrurg: Ah, OK. One thing. It was an issue that was t here with the 2022.04-87 22:28
It was not there with 2022.03
vrurg Not only if you can have A::B::C, but also if it doesn't cause a circular dependency.
Xliff Yes, figured that last bit! :)
vrurg The problem with merging was always there, one way or another. 22:29
Geth rakudo: 4130846be4 | (Vadim Belman)++ | src/Perl6/Optimizer.nqp
Fix cases where we try calling methods on BOOTCode

Triggered by `role A { }; A.new ~~ A:D` code. Thanks @jdv for finding this error!
22:49
rakudo: d4e8b671ab | (Vadim Belman)++ (committed using GitHub Web editor) | src/Perl6/Optimizer.nqp
Merge pull request #4944 from vrurg/fix-optimizer-over-bootcode

Fix cases where we try calling methods on BOOTCode