🦋 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:05 MasterDuke joined
timo the from or to gets set to where the <( or )> was encountered during the matching process, if you want it to have distance from the end or beginning of string you'll have to .* 00:31
it could be made a special case i guess?
00:40 MasterDuke left
ugexe so ive hacked together some stuff in zef to get it to avoid precomp on testing and precomp on install. the bad news it requires a slightly weirder workflow where zef would install to the staging install repo before testing and copying those files when e.g. tests pass 01:50
not quite sure what to do with `zef test ...` though... with such a change that command should also install everything to a staging repo before testing 01:51
02:04 frost left 02:23 _Xliff_ left 03:28 frost joined 04:28 nativecallable6 left, coverable6 left, tellable6 left, quotable6 left, sourceable6 left, greppable6 left, unicodable6 left, evalable6 left, releasable6 left, reportable6 left, notable6 left, benchable6 left, bisectable6 left, committable6 left, squashable6 left, shareable6 left, linkable6 left, statisfiable6 left, bloatable6 left, unicodable6 joined, tellable6 joined, committable6 joined, notable6 joined, coverable6 joined, benchable6 joined 04:29 reportable6 joined, squashable6 joined 04:30 bloatable6 joined, shareable6 joined 04:31 linkable6 joined, quotable6 joined 05:18 SmokeMachine left 05:19 leont left, zostay left 05:20 kawaii_ left, zostay joined 05:22 leont joined, kawaii_ joined 05:28 evalable6 joined 05:29 bisectable6 joined 05:30 releasable6 joined, nativecallable6 joined 05:32 SmokeMachine joined 06:03 reportable6 left 06:06 reportable6 joined 07:30 statisfiable6 joined, greppable6 joined, sourceable6 joined
lizmat Files=1349, Tests=117858, 314 wallclock secs (34.84 usr 9.24 sys + 4274.28 cusr 356.39 csys = 4674.75 CPU) 08:29
08:30 evalable6 left, linkable6 left 08:32 linkable6 joined 09:08 MasterDuke joined 09:15 frost left, frost joined 09:30 evalable6 joined 10:28 frost left 10:38 frost joined 11:38 linkable6 left, evalable6 left 11:40 evalable6 joined
Altai-man releasable6, status 11:56
releasable6 Altai-man, Next release in ≈13 days and ≈7 hours. 3 blockers. Changelog for this release was not started yet
Altai-man, Details: gist.github.com/3c0d2eadb14b25ed4c...03d4d3b112
12:03 reportable6 left 12:04 reportable6 joined 12:40 linkable6 joined 13:06 discord-raku-bot left
gfldex m: class term:<Foo > { }; my \Foo = Foo .new; 13:40
camelia No such method 'new' for invocant of type 'VMNull'. Did you mean
'new'?
in block <unit> at <tmp> line 1
13:56 discord-raku-bot joined 15:22 evalable6 left, linkable6 left 15:25 frost left 18:02 reportable6 left 18:03 reportable6 joined 18:39 squashable6 left 19:24 linkable6 joined 19:25 evalable6 joined 19:42 squashable6 joined
Geth rakudo/fix_stash_threading_issues: 85e1a83b9f | (Stefan Seifert)++ | 5 files
Fix segfaults when multiple threads initialize dynamics

When multiple threads try to access an uninitialized dynamic like $*PROGRAM-NAME at the same time, they all will run the initialization code. This is mostly benign (just a little wasteful) but the actual assignment into the PROCESS:: stash may lead to segfault as that's unsafe writing into a hash. Indeed, this not only affects PROCESS variables, but stashes in general. Since stashes are ... (7 more lines)
19:54
rakudo: niner++ created pull request #4622:
Fix segfaults when multiple threads initialize dynamics
rakudo/fix_stash_threading_issues: db136bc52d | (Stefan Seifert)++ | 5 files
Fix segfaults when multiple threads initialize dynamics

When multiple threads try to access an uninitialized dynamic like $*PROGRAM-NAME at the same time, they all will run the initialization code. This is mostly benign (just a little wasteful) but the actual assignment into the PROCESS:: stash may lead to segfault as that's unsafe writing into a hash. Indeed, this not only affects PROCESS variables, but stashes in general. Since stashes are ... (7 more lines)
20:06
20:22 sena_kun joined 20:23 sena_kun left 20:24 Altai-man left 21:30 evalable6 left, linkable6 left 21:33 linkable6 joined 21:49 squashable6 left 21:52 squashable6 joined 23:27 Kaiepi left
Geth URI: 4ea670e992 | (Geoffrey Broadwell)++ | lib/URI/Query.rakumod
Provide RO value when throwing RO exception

The fixes #48 and has been tested working both before and after the Rakudo merge that exposed the bug.
23:29
23:32 Kaiepi joined, evalable6 joined