🦋 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.
00:02 reportable6 left, reportable6 joined 00:07 kjp joined
japhb Got this building Rakudo HEAD just now: 00:31
t/04-nativecall/02-simple-args.t ................................ Dubious, test returned 1 (wstat 256, 0x100)
No subtests run
nine: ^^
Rebuilt again and it passed this time. Flaky test? 00:38
00:50 kjp left
raydiak apparently that's a bit of a problem child. just at a quick glance there are issues open for failures in that file on ARM, M1 macs, WSL, and clang builds of rakudo on linux 01:04
japhb Ooof 01:21
01:21 kjp joined 02:55 Kaipi left 02:56 Kaipi joined 06:03 reportable6 left, reportable6 joined 06:48 patrickb joined
patrickb o/ 06:57
re yesterdays discussion wrt what to do with the Star Bundle. I'm pretty sure the module list wasn't properly maintained. So yes giving the list some love is in order. 06:59
In my experience the module search has been sufficient to rather quickly find all possible modules to solve a given problem. 07:02
07:03 vrurg_ joined
patrickb To more quickly judge which module to choose it's all a question of which metrics we provide the user. Tests passing is definitely a good thing to have. IIRC we even once had something similar to smoke (automatic test reporting of users test runs) in zef, but it was turned off soon and I thing the corresponding webservice doesn't exist anymore. 07:04
07:05 vrurg left
patrickb Metrics I think would help me to decide which module to use: When was the module initially released? When was the last release? How many releases have there been in total? Upstream and downstream count. 07:07
But that's more of a topic for raku.land. 07:08
07:44 Geth left, Geth joined 07:59 Xliff joined
Xliff o/ 07:59
moon-child \o 08:00
JRaspass Totally agree on the above metrics, I'm tempted to steal the new bus factor from metacpan too 08:17
patrickb JRaspass: Thanks for your work on raku.land! 08:51
lizmat so what is our feeling about this: 08:53
m: for ^10 { LAST last }
camelia ===SORRY!===
last without loop construct
lizmat aka, using control exception constructs inside phasers
m: for ^10 { NEXT last } # there's actually a spectest for this one 08:54
camelia ( no output )
patrickb JRaspass: If I may wish for one more thing: Displaying the ecosystem of a module in the module page and the search list. Workaround is looking in the address bar, so not high prio,but I think it's a good thing to give the ecos some visibility.
JRaspass Oh that's a great idea, I shall add it to the issues 09:00
done, gitlab.com/raku-land/raku-land/-/issues/6
patrickb Yay! 09:01
tbrowder hi, looking at raku.land i see dups on prolific author list 09:22
JRaspass: ++ for raku.land, esp for the alpha sorted list! 09:24
if you're looking for suggestion: add sort by date of publishing 09:26
correction, the dups are on the popular dist list 09:28
09:45 frost joined 10:59 Kaipi left 11:00 Kaipi joined 11:14 frost left 11:28 frost joined 12:02 reportable6 left 12:03 reportable6 joined
tbrowder .tell JRaspass ^^^ 12:56
tellable6 tbrowder, I'll pass your message to JRaspass 12:57
tbrowder .ask lizmat is there an issue with my rakudo docs PR #4441? my intent was to get published pretty much as is and let you experts add to it--a living WIP 13:01
tellable6 tbrowder, I'll pass your message to lizmat
14:51 melezhik joined
melezhik . 14:51
releasable: status
releasable6 melezhik, Next release in ≈15 days and ≈4 hours. 1 blocker. Changelog for this release was not started yet
melezhik, Details: gist.github.com/b4816c38719559d3b1...165907813a
gfldex lizmat: `LAST last` That one is tricky. Because it's a NOP, and such could be implemented as a NOP, but is also most likely a mistake. In a dynamically optimised language any NOP should vanish. I would impelent it as a NOP and warn. 15:04
lizmat: The tricky one is `NEXT next` because that can have side effects and therefore must be executed. But again, it can also be a mistake. 15:06
15:09 melezhik left
Geth rakudo/new-disp: cb029f1a51 | (Jonathan Worthington)++ | 4 files
Start adapting Raku to always use new-disp on Moar

Switch all the places that were guarded by an environment variable to instead be VM conditional. The code to make callmethod compile into a dispatch op goes away, as NQP on MoarVM will now do that by default (and also for call ops).
rakudo/new-disp: 9e66de3ac6 | (Jonathan Worthington)++ | src/Perl6/bootstrap.c/BOOTSTRAP.nqp
Use NQP dispatchers as Raku ones during bootstrap

Just to get us through the dispatches we need to do during the process of setting things up. Since we don't currently wrap any code objects up as Raku ones, and the meta-objects are compatible so far as using the
  `find_method` API goes, this is good enough.
15:47 patrickb left
leont Oooh 15:48
16:11 smarton left, smarton joined 17:25 Kaipi left 17:26 Kaipi joined, cognominal joined 18:02 reportable6 left 18:03 reportable6 joined 18:45 Kaipi left, Kaipi joined 18:47 Kaipi left, Kaipi joined 18:50 Kaipi left, Kaipi joined 20:09 Xliff left 22:34 dogbert17 left 22:53 Kaiepi joined, Kaipi left