🦋 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:03 reportable6 left 00:05 reportable6 joined 06:02 reportable6 left 06:05 reportable6 joined
[TuxCM] Rakudo v2021.06-18-gad94ef1d6 (v6.d) on MoarVM 2021.06-6-g6977d0591
csv-ip5xs0.856 - 0.874
csv-ip5xs-209.310 - 9.685
csv-parser29.439 - 29.513
csv-test-xs-200.379 - 0.381
test8.074 - 8.582
test-t2.100 - 2.111
test-t --race1.054 - 1.054
test-t-2036.014 - 36.069
test-t-20 --race11.095 - 11.520
gfldex I'm looking for the spot in Rakudos source where Junctions are handled. Any pointers are very welcome. 08:10
moon-child core.c/Junction.pm6:311 AUTOTHREAD, maybe? 08:14
oh, and p6setautothreader 08:17
gfldex I'm specifically looking for the spot where the compiler goes "ohh, I'm not going to throw a type error but turn this thing inside out to handle the Junction.". 08:18
moon-child ClassHOW.nqp:289, find_method_fallback 08:20
gfldex I was grepping for Junction not junction. :-/ 08:22
Thanks a lot!
moon-child :) 08:23
10:30 AlexDaniel joined 12:02 reportable6 left 12:03 reportable6 joined 13:01 guifa left 14:17 dogbert17 left
tonyo should add a flag to make grep case insensitive 14:52
ugexe that would be a string comparison thing, not a grep thing 14:55
14:56 melezhik joined
melezhik . 14:56
releasable: status
releasable6 melezhik, Next release in ≈28 days and ≈4 hours. 1 blocker. Changelog for this release was not started yet
melezhik, Details: gist.github.com/898756da0aef133bc5...7fdc823d13
15:05 frost left
tonyo grep the utility, not in method in raku 15:46
lizmat grep has -i , no? 15:47
15:57 donaldh joined 16:33 donaldh left 17:16 djinni` left 17:17 djinni` joined 18:02 reportable6 left 18:05 reportable6 joined 18:21 dogbert17 joined
melezhik I always wonder the logic how next release change log is created? the one I get by releasable status 19:55
is it manually crafted? I don't see any tags on respected GH issues or PRs ... 19:56
raydiak pretty sure it's just the titles of all commits since the last release. same things you see at github.com/rakudo/rakudo/commits/master 20:05
MasterDuke but yeah, it's at least semi-manually crafted 20:07
github.com/rakudo/rakudo/wiki/ChangeLog-Draft this is filled in 20:08
raydiak the final one for release is, but I assume it's not hand-massaged for the releasable bot, is it? 20:09
melezhik so based on commits data? thanks 20:12
raydiak you're welcome. if you want to check out precisely what the bot is doing for yourself, the code is at github.com/Raku/whateverable/blob/...easable.p6 . most of the other bots are also in that repo 20:13
melezhik raydiak thanks, the question was more about the logic, but yeah, thanks
I am just playing with r3 and trying to assign tags to my tests so that I could run something like `tomty --only=rc_2021_07+closed` and was wandering how commits,closed GH issue would go into final release ... 20:15
raydiak I just mean, the code would be the authority wrt the logic :) there could be more to the story than I'm aware of. but yes afaik, it's just the commit log. not PRs or issues. the *final* changelog with the rakudo releases is somewhat edited by humans, though 20:17
melezhik yeah, sure
21:33 melezhik left 22:24 m6502 joined
raydiak hit a flapper in t/spec/S02-types/mix.t, #126 on moar. known? 22:53
23:16 m6502 left 23:24 melezhik joined 23:30 melezhik left
raydiak then again, I've been running it in a loop for over half an hour since and can't reproduce it, so... 23:53