[00:02] *** lucasb left [00:14] *** Kaiepi left [00:15] *** Kaiepi joined [00:21] *** Kaiepi left [00:21] *** Kaiepi joined [00:50] *** |Tux| joined [00:51] greppable6: [00:51] vrurg, 74 lines, 22 modules: https://gist.github.com/3b2631c1b3781a4a813e56b097cebb24 [01:10] https://cdn.discordapp.com/attachments/538774203378171935/637095202594488320/unknown.png - in the network view you can now set a color and icon for every type of collectable <3 [01:14] *** b2gills joined [01:43] !! [02:11] <[Coke]> timotimo++ [04:19] *** Kaiepi left [04:20] *** Kaiepi joined [05:45] tbrowder: doing Positional and Associative sounds rather straight forward? class Foo does Positional does Associative { method of() { Mu }; method ASSIGN-POS($i, \a) {}; method ASSIGN-KEY($k, \a) {}; }; Foo.new[0] = 1; Foo.new = 1; [05:45] tbrowder: what issues are you encountering? [06:52] *** Xliff joined [06:53] o/ [06:54] *** sena_kun joined [06:55] .tell AlexDaniel Noted loss of performance in benchmarking tests for p6-Pango. See recent (https://github.com/Xliff/p6-Pango/blob/master/stats/LastBuildResults-20191025) and previous (https://github.com/Xliff/p6-Pango/blob/master/stats/LastBuildResults-20191017) [06:55] Xliff, I'll pass your message to AlexDaniel [06:56] .tell AlexDaniel That's 21 second compile time increase over the last week or so... FYI [06:56] Xliff, I'll pass your message to AlexDaniel [06:57] *** Xliff left [09:28] *** moon_child is now known as elronnd [09:29] *** elronnd is now known as moon_child [10:07] *** pmurias joined [10:45] *** pmurias left [10:48] *** pmurias joined [11:10] *** ggoebel joined [11:21] *** ggoebel left [11:54] *** ggoebel joined [12:05] nine: the problem is the class needs to be in nqp in rakudo/src/Perl6/*.nqp where $=data is created. i don't see how it can be done otherwise, but of course i certainly don't claim to be an expert here. [12:06] i'm just looking at how $=pod is created and exploring a parallel path. [13:18] *** lucasb joined [13:25] ¦ nqp/truffle: 5 commits pushed by (Paweł Murias)++ [13:25] ¦ nqp/truffle: 6e9c512ba1 | [truffle] smart intify type objects [13:25] ¦ nqp/truffle: 68ac35df87 | [truffle] smart numify type objects [13:25] ¦ nqp/truffle: 4dedc452b2 | [truffle] Deserialize VMArrays of objects [13:25] ¦ nqp/truffle: 3ddfeceb29 | [truffle] Run passing tests [13:25] ¦ nqp/truffle: 666c0cb81b | [truffle] Implement nqp::bindcomp and nqp::getcomp [13:25] ¦ nqp/truffle: review: https://github.com/perl6/nqp/compare/4f74b67d58f2...666c0cb81b98 [13:33] *** ggoebel left [13:47] Xliff: oook… can you bisect it? [13:47] AlexDaniel, I'll pass your message to Xliff [13:48] Xliff: so it's between 2019.07.1-443-gcfc0f46c0 2019.07.1-398-gf3dda96a8, right? [13:48] AlexDaniel, I'll pass your message to Xliff [13:48] *** [Coke] joined [14:02] *** [Coke] left [14:09] *** [Coke] joined [14:09] *** [Coke] left [14:09] *** [Coke] joined [14:32] ¦ nqp/truffle: 258f5f4888 | (Paweł Murias)++ | src/core/YOUAREHERE.nqp [14:32] ¦ nqp/truffle: [truffle] Install a stub compiler with nqp::bindcomp [14:32] ¦ nqp/truffle: [14:32] ¦ nqp/truffle: This makes nqp::getcomp('nqp').backend.name work [14:32] ¦ nqp/truffle: review: https://github.com/perl6/nqp/commit/258f5f4888 [14:32] ¦ nqp/truffle: 0263bdf7de | (Paweł Murias)++ | src/vm/jvm/bin/run_tests.pl [14:32] ¦ nqp/truffle: [truffle] Add assing tets 109 [14:32] ¦ nqp/truffle: review: https://github.com/perl6/nqp/commit/0263bdf7de [14:40] *** Kaeipi joined [14:42] *** Kaiepi left [14:42] Been there, done that typo before... :) [14:42] pmurias++ [14:42] (The ++ for the hacking, not the typo :P) [15:05] tbrowder: Capture is created in the BOOTSTRAP and allows both positional and associative access (though it doesn't do those roles). If you need there roles, there's a precedent for Positional: https://github.com/rakudo/rakudo/blob/master/src/Perl6/bootstrap.c/BOOTSTRAP.nqp#L143 [15:11] *** pmurias left [15:15] nine: thanks! [15:30] *** patrickb joined [16:32] *** TreyHarris joined [16:34] *** MasterDuke joined [17:07] *** ggoebel joined [17:31] *** ggoebel left [18:32] Is it bad when raku creates the core repository folders already during the build and not only at install time? [18:32] 2019-10-21T22:07:58Z #perl6-dev patrickb specfile is the source files that tell the rpmbuilder how to create an rpm [18:35] patrickb: I think it is if they're created outside of the base dir. [18:37] There is a conflict of interest. On the one side we don't want the build raku to not touch the install folders, but on the other hand we want it to be able to use the install repo. [18:40] Use for what? Inline::Perl5? [18:49] *** ggoebel joined [18:50] Yup. [19:08] patrickb: Can't we have it installed locally within base dir somehow? [19:10] We could. It's mostly a question of what we want. If we want the build dir raku to have access to the full repo in the install dir, then installing Inline::Perl5 into basedir isn't going to help. [19:12] patrickb: I don't like the idea of rakudo accessing the install dir prior installation. What if the version we build isn't compatible with the installed one and mangles with the main repo in non-revertible way? [19:12] summon nine [19:14] https://wakelift.de/p/c3f095d6-8827-426f-9d0e-d2c1a230731d/ - i would welcome a bit of proofreading/review of my latest grant report [19:14] vrurg: I agree. How could an alternative look? I the only need actually Inline::Perl5? Or are there other modules we might access from the build dir? [19:16] timotimo: I left a tab opened. [19:18] patrickb: The alternative would be using, say, blib as a file repository. Whatever we need at compile time – we know about it. Whatever somebody needs for testing – he can use -I [19:19] Then https://github.com/rakudo/rakudo/pull/3236 is already the final solution. [19:21] patrickb: perhaps. I can't get deeper into it now though. [19:21] I think nine needs to give his oppinion on this. He's the original reporter of the bug/problem. [19:22] vrurg: hum? [19:23] timotimo: opened your link, left it opened to read later. :) [19:24] ah, ok [19:24] thank you [19:24] timotimo: BTW, I have pinpointed the run-away closure problem and even kinda fixed it a few minutes ago. [19:24] oh, nice [19:24] looking forward to reading all about it in a commit message, or on channel, or whereever :) [19:24] for now i'll be AFK a bit [19:25] But might need more help because it seemingly breaks nativecall test in rakudo. But this I need to check out carefully because with the amount of the debug stuff I put into the core anything could happen. [19:28] patrickb: I'll try to remember about the issue. Perhaps would find a better solution to the outside dirs. But in general, the only good one is to build everything into blib. Anything else is a hack. [19:29] Correspondingly, modules needed during build/test stage must go into blib too. [19:29] *** pmurias joined [19:33] kawaii: results? [19:53] timotimo: only comment (other than nice post) is that when i first saw "Network View" with information about layers, i assumed you mean the internet kind of network and were referring to the OSI layers [20:08] timotimo: "for some reason it's still around" perhaps better: "for some reason is still around" [20:08] (1st rime) [20:10] hmmm... stroopwafel [20:12] timotimo++ [20:13] <[Coke]> lizmat... thank you for reminding me to ask my local baker if he can make some stroopwafel [20:16] *** sena_kun left [20:16] *** releasable6 left [20:21] *** greppable6_ joined [20:21] *** greppable6_ left [20:25] *** releasable6 joined [20:27] thanks MasterDuke, lizmat [20:29] *** |Tux| left [20:29] i seem to have been using "panel" and "pane" interchangably and inconsistently [20:29] what should i be calling what? [20:40] *** Kaeipi left [20:41] *** Kaeipi joined [21:05] ¦ rakudo: Kaiepi++ created pull request #3269: [WIP] Ensure CArray and Pointer can be parameterized with non-Any types [21:05] ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/3269 [21:11] It might make sense to merge https://github.com/rakudo/rakudo/pull/3236 pre release. Opinions? [21:15] vrurg: ↑ [21:16] patrickb: “This is not wanted.” why is it not wanted? I don't get it [21:17] patrickb: like, what's exactly wrong with putting stuff into build_dir/share/perl6 ? [21:31] nope it's build_dir/../share/perl6 [21:31] and that's not wanted. [21:31] patrickb: so the PR description is wrong? [21:31] I'm confused [21:31] ah! I misstyped that! [21:31] Yes, it's wrong. [21:32] so TL;DR build process writes outside the build dir [21:32] you can fix the commit description if you want, then I think we can merge [21:33] Already did! [21:35] patrickb: that's just the PR description, not the commit :) [21:35] Ugh, right [21:35] gimme a moment [21:38] OK. Now I fixed the commit msg. [21:44] patrickb: any other possible solutions besides tweaking environ? [21:45] not that I see any issue with it, it just feels like an asswards way of doing it :) [22:12] AlexDaniel: it's not a good way. But currently it's the only way to do it without moving the whole build destination into blib. [22:25] *** pmurias left [22:27] *** pmurias joined [22:38] vrurg: so we just merge it? [22:38] Yes, for now. [22:38] OK [22:39] As I'm done with run-away closures, I might consider changing tasks and do the switch into blib. [22:39] Though I expect some opposition to this. As always... [22:41] ¦ rakudo: cbd1dc2776 | (Patrick Böker)++ | 2 files [22:41] ¦ rakudo: Don't put CompUnitRepo folders outside the build dir during build [22:41] ¦ rakudo: [22:41] ¦ rakudo: CompUnitRepo generates a folder structure in the PERL6_HOME folder. That [22:41] ¦ rakudo: folder does not exist yet during the build. So the normal logic to [22:41] ¦ rakudo: auto determine the PERL6_HOME folder thinks it's [22:41] ¦ rakudo: `build_dir/../share/perl6`. Thus CompUnitRepo puts some folders there. [22:41] ¦ rakudo: This is not wanted. As a temporary solution to prevent pollution of the [22:41] ¦ rakudo: users directories, we just explicitly set PERL6_HOME to [22:41] ¦ rakudo: `build_dir/gen/dummy_p6_home` then CompUnitRepo can litter it's folders [22:41] ¦ rakudo: there and all is well. [22:41] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/cbd1dc2776 [22:41] ¦ rakudo: afbe64a436 | (Aleks-Daniel Jakimenko-Aleksejev)++ (committed using GitHub Web editor) | 2 files [22:41] ¦ rakudo: Merge pull request #3236 from patzim/no-folder-litter [22:41] ¦ rakudo: [22:41] ¦ rakudo: Don't put CompUnitRepo folders outside the build dir during build [22:41] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/afbe64a436 [22:45] *** toddr joined [22:46] off to bed [22:46] Howdy, I've been asked to help import the perl 6 RT tickets from github. I can't recall who asked me to do so. I need to know what the best place to put the tickets would be. [22:47] While you can transfer the tickets within the org, it's not simple so it might be best to put the majority of them in the right place to begin with. [22:48] *** patrickb left [22:54] AlexDaniel: I think you know the answer to ^^? [22:54] toddr: hi! :) [22:54] toddr: so, as we discussed, let's put them on https://github.com/perl6/old-issue-tracker and see how it goes? [22:55] toddr: for the first demo run, then I'll let you know the final destination [22:55] toddr: is this plan ok for you? [22:55] I guess so. [22:56] ok I'll start looking and will get back to you. [23:00] jnthn: while you're here, can you have a quick look at this [23:00] ¦ problem-solving/old-issue-tracker: b6730fe2e9 | (Aleks-Daniel Jakimenko-Aleksejev)++ | solutions/infrastructure/Old-Issue-Tracker-Dismantling-Plan.md [23:00] ¦ problem-solving/old-issue-tracker: First draft of the RT tracker dismantling plan [23:00] ¦ problem-solving/old-issue-tracker: review: https://github.com/perl6/problem-solving/commit/b6730fe2e9 [23:02] jnthn: https://github.com/perl6/problem-solving/commit/b6730fe2e9?short_path=721020b#diff-721020baec851dadda7a7379dc0f7018 [23:04] let me test this real quick… [23:05] ¦ roast/rakudo_2897_fix: c92b752668 | (Vadim Belman)++ | 3 files [23:05] ¦ roast/rakudo_2897_fix: Test for precompiled closures [23:05] ¦ roast/rakudo_2897_fix: [23:05] ¦ roast/rakudo_2897_fix: In support of MoarMV/MoarVM#1209 [23:05] ¦ roast/rakudo_2897_fix: [23:05] ¦ roast/rakudo_2897_fix: Related to rakudo/rakudo#2897 and a number of other tickets. [23:05] ¦ roast/rakudo_2897_fix: review: https://github.com/perl6/roast/commit/c92b752668 [23:05] ¦ roast: vrurg++ created pull request #593: Test for precompiled closures [23:05] ¦ roast: review: https://github.com/perl6/roast/pull/593 [23:07] jnthn: proof that it works: [23:07] https://github.com/perl6/deleteme-test-repo/issues/1 [23:07] https://github.com/perl6/deleteme-test-repo [23:07] so first the ticket was moved to a different repo, then the first repo was moved to a different org [23:07] and the redirect stays [23:07] AlexDaniel: +1 [23:08] AlexDaniel: The plan feels fine to me. [23:08] AlexDaniel++ toddr++ [23:09] jnthn: alright I'll submit it as a PR then, I hope we won't need to wait for 2 weeks though this time :D [23:09] Will review it right away once you submit [23:09] jnthn: is it more `infrastructure` or `rakudo` ? [23:10] Well, most (though not all) of the issues relate to Rakudo [23:10] rba: will submit it as a rakudo issue, unless you object [23:12] toddr: sorry it took so long to figure it out for such a simple issue, we were a bit busy with other stuff [23:17] *** redable joined [23:19] *** redable left [23:20] who is James Cloos and why did he subscribe to the old-issue-tracker repo [23:21] toddr: I can delete and recreate the repo to save this poor soul [23:21] *** redable joined [23:21] it's fine. I'm not going to get it done for a couple of days. [23:21] p5 migration is done though. [23:23] *** redable left [23:27] *** redable joined [23:28] *** redable left [23:31] *** redable joined [23:32] *** redable left [23:33] *** redable joined [23:33] *** redable left [23:34] *** epony joined [23:34] https://wakelift.de/2019/10/26/introducing-the-heap-snapshot-ui/ - lol i blogged [23:35] *** pmurias left [23:42] ¦ problem-solving/old-issue-tracker: 5ccebce4b1 | (Aleks-Daniel Jakimenko-Aleksejev)++ | solutions/rakudo/Old-Issue-Tracker-Dismantling-Plan.md [23:42] ¦ problem-solving/old-issue-tracker: Add the RT tracker dismantling plan [23:42] ¦ problem-solving/old-issue-tracker: review: https://github.com/perl6/problem-solving/commit/5ccebce4b1 [23:43] ¦ problem-solving/old-issue-tracker: 2ff1bb88f0 | (Aleks-Daniel Jakimenko-Aleksejev)++ | solutions/rakudo/Old-Issue-Tracker-Dismantling-Plan.md [23:43] ¦ problem-solving/old-issue-tracker: Add the RT tracker dismantling plan [23:43] ¦ problem-solving/old-issue-tracker: [23:43] ¦ problem-solving/old-issue-tracker: Closes #49. [23:43] ¦ problem-solving/old-issue-tracker: review: https://github.com/perl6/problem-solving/commit/2ff1bb88f0 [23:43] ¦ problem-solving: AlexDaniel++ created pull request #126: Add the RT tracker dismantling plan [23:43] ¦ problem-solving: review: https://github.com/perl6/problem-solving/pull/126 [23:45] ¦ problem-solving: AlexDaniel unassigned from rba Issue rt.perl.org is shutting down https://github.com/perl6/problem-solving/issues/49 [23:45] ¦ problem-solving: AlexDaniel unassigned from maettu Issue rt.perl.org is shutting down https://github.com/perl6/problem-solving/issues/49 [23:45] ¦ problem-solving: AlexDaniel assigned to jnthn Issue rt.perl.org is shutting down https://github.com/perl6/problem-solving/issues/49 [23:47] *** redable joined