00:38 nativecallable6 left, statisfiable6 left, quotable6 left, tellable6 left, greppable6 left, bloatable6 left, releasable6 left, squashable6 left, benchable6 left, committable6 left, evalable6 left, sourceable6 left, linkable6 left, unicodable6 left, notable6 left, coverable6 left, reportable6 left, bisectable6 left, shareable6 left, shareable6 joined 00:39 benchable6 joined, statisfiable6 joined, greppable6 joined, nativecallable6 joined 00:40 sourceable6 joined, squashable6 joined, bisectable6 joined, bloatable6 joined, coverable6 joined, reportable6 joined, linkable6 joined, committable6 joined, unicodable6 joined 00:41 releasable6 joined
Xliff MasterDuke: Don't know. Didn't know about it until you mentioned it. 00:41
I'll have to take a look at it, later.
00:41 notable6 joined
Xliff I've been stuck in the weeds for hours with no solution. 00:41
00:41 tellable6 joined, evalable6 joined, quotable6 joined
Xliff MasterDuke: Thanks for letting me know, though! :) 00:42
02:35 releasable6 left, bloatable6 left, unicodable6 left, tellable6 left, nativecallable6 left, benchable6 left, evalable6 left, bisectable6 left, notable6 left, coverable6 left, statisfiable6 left, quotable6 left, sourceable6 left, linkable6 left, reportable6 left, committable6 left, shareable6 left, greppable6 left, squashable6 left, greppable6 joined, nativecallable6 joined, releasable6 joined 02:36 shareable6 joined, bisectable6 joined, notable6 joined, coverable6 joined, evalable6 joined, tellable6 joined, quotable6 joined, sourceable6 joined 02:37 committable6 joined, benchable6 joined, bloatable6 joined, reportable6 joined, statisfiable6 joined, squashable6 joined 02:38 unicodable6 joined, linkable6 joined 04:09 notable6 left, benchable6 left, linkable6 left, sourceable6 left, greppable6 left, quotable6 left, committable6 left, evalable6 left, shareable6 left, bisectable6 left, tellable6 left, bloatable6 left, unicodable6 left, reportable6 left, statisfiable6 left, nativecallable6 left, greppable6 joined, reportable6 joined 04:10 evalable6 joined, quotable6 joined, bisectable6 joined 04:11 shareable6 joined, nativecallable6 joined, statisfiable6 joined, sourceable6 joined, bloatable6 joined, notable6 joined 04:12 committable6 joined, linkable6 joined, tellable6 joined, benchable6 joined, unicodable6 joined 04:43 MasterDuke left 06:10 interwebs left 06:43 codesections left 06:44 codesections joined 07:03 Altai-man joined 07:19 sena_kun joined 07:21 Altai-man left
Xliff gist.github.com/Xliff/b27f77e33539...9c28c4ed68 <- Help, please? 08:34
nine Xliff: yes, runtime is too late. Also this sounds like a question better suited for #raku 08:36
lizmat Files=1336, Tests=113586, 223 wallclock secs (29.62 usr 8.48 sys + 3102.68 cusr 288.28 csys = 3429.06 CPU) 08:57
Xliff nine: Thanks. I've posted this twice in raku and no one responded.
So I would have to implement a run-time version of handles, then? 08:58
09:19 Kaiepi left 09:21 Kaeipi joined
nwc10 Is there an easy Rakudo way to generate the sort of information that is in: 09:21
This is perl 5, version 16, subversion 3 (v5.16.3) built for ppc64-linux-thread-multi
particularly the architecture thingy (versions are boring) 09:22
alhgough I guess that Perl 5 has more "fun" in its architecture, because "thread" and "multi" are both Configure-time choices
whereas MoarVM is MoarVM is MoarVM
09:28 Kaeipi left
lizmat nwc10: perhaps somewhere in say .key ~ ": " ~ .value for $*VM.config.pairs.sort ? 09:29
09:29 Kaiepi joined
nwc10 $*VM.config.<osvers> seems to be the most useful 09:31
OK, interesting. 09:32
nothing in $*VM.config seems to be able to report whether MoarVM is built with a 32 or 64 bit ABI
that's probably actually a bug. 09:33
because it's possible to build either on (at least) x86_64, ppc64 and sparc64 (And I assume also mips64 and aarch64)
and we have no way of filtering user bug reports based on which way someone else built their MoarVM
in that, I have build rakdudo on both 3.10.0-957.27.2.el7.ppc64 and 3.10.0-957.27.2.el7.ppc64 :-) 09:35
spot the difference.
and, even more WTF - I've built it for: 4.19.0 09:40
(ooh, and my local machine reports 4.9.0)
I'm not even sure *where* theose numbers are coming from. I guess I should go did, as they are considerably LTA 09:41
chocolate-teapot LTA
10:06 Kaeipi joined 10:07 Kaiepi left 10:10 Kaeipi left 10:20 MasterDuke joined
MasterDuke nwc10: does the `-V` option to raku show anything useful? 10:21
lizmat MasterDuke: afaik, that just dumps $*VM.config 10:22
nine We probably also want to report whether rakudo is build relocatably 10:43
Geth rakudo: lizmat++ created pull request #3907:
Parallel module install
[TuxCM] Rakudo version 2020.08.2-59-ge65466fcd - MoarVM version 2020.08-91-g590bac47e
csv-ip5xs0.968 - 0.991
csv-ip5xs-2010.161 - 10.177
csv-parser25.464 - 27.605
csv-test-xs-200.390 - 0.390
test7.752 - 7.885
test-t1.899 - 1.928
test-t --race0.847 - 0.927
test-t-2033.178 - 33.938
test-t-20 --race9.170 - 9.858
11:18 Altai-man joined 11:20 sena_kun left
Geth ¦ problem-solving: tbrowder assigned to rba Issue Add a Raku blog site as "blogs.raku.org" github.com/Raku/problem-solving/issues/231 11:52
¦ problem-solving: lizmat unassigned from rba Issue Add a Raku blog site as "blogs.raku.org" github.com/Raku/problem-solving/issues/231 11:54
12:16 domidumont joined 12:30 Kaeipi joined 12:31 Kaiepi joined 12:32 soularis joined 12:33 soularis left
Kaiepi with my dns pr, i find myself having to go back and redo chunks of changes every now and then when i change my mind about how parts of it should work, which wastes a lot of time 12:45
i skimmed over jnthn++'s rakuast pr and noticed he hardly does anything like this though... are there things you guys do to avoid this?
ugexe m: say $*KERNEL.arch 12:57
camelia x86_64
tellable6 2020-09-01T14:05:54Z #raku <[Coke]> ugexe do you accept tony-o's nomination, btw?
MasterDuke Kaiepi: i often change stuff too, but it isn't always visible because i may do a lot of local rebasing/merging/deleting/etc commits before pushing 13:24
Kaiepi ah 13:37
nine Kaiepi: from what I know jnthn takes much time to think things through before starting with the implementation. See for example his design documents for the new dispatching mechanism in MoarVM 13:38
Personally I have two distinct modes of operation, depending on my familiarity with the subject. When designing an API I also like to take much time beforehand, preferrably away from the keyboard to get at a good design. This is for an area where I know most of what's involved. 13:42
The other way is a kind of exploratory implementation, where I discover mostly through trial and error. That's for areas where I lack most of the expertise like "let's jump in and fix BEGIN time EVAL" 13:43
In the latter case git rebase -i is my best friend :) 13:44
13:56 domidumont left, domidumont joined 14:01 domidumont left 15:19 sena_kun joined 15:20 Altai-man left 15:43 domidumont joined 16:04 domidumont left 16:06 domidumont joined
[Coke] Reminder: Voting for RSC is open 16:14
Geth rakudo/rakuast: 926e02904c | (Jonathan Worthington)++ | 4 files
RakuAST handling of dotty infixen (`.`, `.=`)

This handles the cases where they are parsed as infixes.
16:48 lizmat left 16:49 lizmat joined 16:57 Summertime joined
Geth rakudo/rakuast: df8f7b28ae | (Jonathan Worthington)++ | 6 files
RakuAST handling of capture terms
18:39 domidumont left 19:18 Altai-man joined 19:20 sena_kun left 20:49 Altai-man left 21:05 wildtrees joined 21:10 wildtrees_ joined 21:11 wildtrees left 21:14 wildtrees__ joined
lizmat and another Rakudo Weekly News hits the Net: rakudoweekly.blog/2020/09/07/2020-...ime-again/ 21:15
21:17 wildtrees_ left 21:21 wildtrees_ joined, Kaeipi left, Kaiepi left 21:23 wildtrees__ left 21:28 Kaiepi joined 21:35 wildtrees__ joined, wildtrees__ left 21:36 wildtrees_ left, wildtrees joined 21:37 wildtrees left 21:52 pamplemousse joined 22:07 pamplemousse left 22:10 pamplemousse joined
[Coke] lizmat++ 22:14
22:24 pamplemousse left 23:00 leont left 23:23 lizmat left, lizmat joined