[00:02] *** sena_kun left [00:28] jnthn: speaking of operators, what we do actually need is an op that checks for Nil before calling a method [00:28] I think in Ruby that's &. [00:29] for example: [00:30] die ‘No joystick device found!’ unless $input-device&.IO.e [00:30] if you know how to write that right now without `and` please let me know :) [00:30] because I have this kind of stuff all over my code [00:31] actually, in this case .? sorta works? [00:32] m: say Nil.IO [00:32] rakudo-moar 7e7aa2626: OUTPUT: «(Path)␤» [00:32] m: say Nil.?IO [00:32] rakudo-moar 7e7aa2626: OUTPUT: «(Path)␤» [00:33] m: say Nil.?IO.e [00:33] rakudo-moar 7e7aa2626: OUTPUT: «Invocant of method 'e' must be an object instance of type 'IO::Path', not a type object of type 'IO::Path'. Did you forget a '.new'?␤ in block at line 1␤␤» [00:33] ok, it sorta doesn't [01:24] AlexDaniel: sounds like you need 'invoke if defined' kind of thing. [01:28] AlexDaniel: There is an op for you. It's called andthen. [01:28] m: my $foo; die "ok" unless $foo andthen .IO.e; [01:28] rakudo-moar 7e7aa2626: OUTPUT: «ok␤ in block at line 1␤␤» [01:29] m: my $foo = "no-file"; die "ok" unless $foo andthen .IO.e; [01:29] rakudo-moar 7e7aa2626: OUTPUT: «ok␤ in block at line 1␤␤» [01:29] oh [01:30] It's the first time I see a real use for it. [01:35] so [01:35] die ‘No joystick device found!’ unless $input-device andthen .IO.e; [01:36] I think it is. [01:39] geez that's a weird operator :D [01:39] but I honestly didn't realize that I could use it this way [01:39] alright [01:41] I think there was a discussion about removing it somewhere. Or was it about `notandthen`? Can't really remember now. [01:44] AlexDaniel: BTW, an example in the docs is about your situation: https://docs.perl6.org/language/operators#infix_notandthen [01:47] “At first glance, notandthen might appear to be the same thing as the orelse operator. The difference is subtle” [01:47] yeah, I remember reading this [01:47] and then not using any of these :D [01:49] Me too. Though I probably spend ~60-70% or my time in NQP lately... [01:55] sounds like you're not using raku in production enough! [01:55] :) [02:01] It is how things are now. [02:03] I've some spare time on my hands and trying to use as much of it as possible for bug fixing. [02:03] *I've got [02:05] Hm, is there a dumper for moar precompiled files? [02:15] vrurg++ [03:00] ¦ problem-solving: 7af1dfc3f9 | (Fernando Correa de Oliveira)++ (committed by Aleks-Daniel Jakimenko-Aleksejev) | README.md [03:00] ¦ problem-solving: Add my name to the list [03:00] ¦ problem-solving: review: https://github.com/perl6/problem-solving/commit/7af1dfc3f9 [03:00] ¦ problem-solving: 5e9d288a3b | (Aleks-Daniel Jakimenko-Aleksejev)++ (committed using GitHub Web editor) | README.md [03:00] ¦ problem-solving: Merge pull request #84 from perl6/merge-mishap [03:00] ¦ problem-solving: [03:00] ¦ problem-solving: Add FCO to the list [03:00] ¦ problem-solving: review: https://github.com/perl6/problem-solving/commit/5e9d288a3b [03:01] ¦ problem-solving/master: 4 commits pushed by (Vadim Belman)++, (Aleks-Daniel Jakimenko-Aleksejev)++ [03:01] ¦ problem-solving/master: 6a1a9d9086 | Add vrurg to the list [03:01] ¦ problem-solving/master: 3b70d4006b | Remove myself from label-assignment [03:01] ¦ problem-solving/master: 0b9098d3e6 | Merge branch 'master' into add_vrurg [03:01] ¦ problem-solving/master: 6d0c078ea0 | Merge pull request #87 from vrurg/add_vrurg [03:01] ¦ problem-solving/master: review: https://github.com/perl6/problem-solving/compare/5e9d288a3bdd...6d0c078ea04d [03:05] AlexDaniel: it means less time for the bugs now. [03:06] weekly: Welcome @FCO and @vrurg to the list of problem-solving reviewers! https://github.com/perl6/problem-solving/pull/84 https://github.com/perl6/problem-solving/pull/87 [03:06] AlexDaniel, Noted! (weekly) [03:06] SmokeMachine: ↑ [03:06] :) [03:06] vrurg: what do you mean? [03:07] I guess, roast and language release process are my direct responsibility now. [03:09] vrurg: well, being on that list simply means that you need to review stuff… you can still send everyone to jnthn :D [03:10] not how it should be, but I guess things will improve as more people get involved with stuff :) [03:10] AlexDaniel: I applied for the reason to take over the language release management. Thus, I consider it my duty now. [03:11] vrurg: yeah, but we haven't added a new label yet https://github.com/perl6/problem-solving/pull/87#issuecomment-541940054 [03:12] so tickets will still be assigned to jnthn by default [03:12] I guess jnthn will reassign anything that belongs to you? [03:13] The label is one part of the overall process. I would need to think of it in general. Like, I tried to implement a project management on my fork of problem-solving. [03:14] nice! [03:14] It's up to jnthn, of course. [03:14] speaking of time, I won't have any this week :( [03:15] like, at all [03:15] there are release braches in nqp and rakudo, so once moarvm is released nobody should feel blocked by lack of release [03:15] Something good, I hope? [03:16] vrurg: no, just wörk (ish), but generally life is good :) [03:17] btw if anyone is interested, previously I said that I'll have to do alternative service in my country starting Jan 2020 [03:17] but that's no longer the case! [03:17] I'm now free till at least Nov 2020, and a bit more after that, and possibly forever [03:17] Oh, unblocking merges! Eventually! BTW, will you have time for commenting on issues/PRs? I hope to get jnthn a bit more involved into the operators discussion. Your opposition could be useful. [03:18] hah, useful opposition :) [03:18] vrurg: I'll try. Thing is, we already have .+ and .?, which I didn't really know about [03:18] It is always useful. Total consensus is the direct path to swamping death. Prooved by USSR. [03:18] like I knew about .? but kinda forgot about .+ [03:19] vrurg: some time ago Zoffix proposed this idea that whenever you add a new feature you have to remove one too :) [03:19] which is a bit extreme, but it's true that currently we're only adding and not removing anything [03:19] I was saying it once, .+ is pretty much useless without fully implemented submethods. It would have more reasons to be used with my PR. [03:20] Oh, the new ops make .* obsolete. I would gladly remove it. [03:20] Can I do it tomorrow??? Pleeeeeaseeee?! :D [03:21] and somehow lately I really want to just delete and simplify stuff… [03:22] “Raku” change is very refreshing :) [03:23] no need for no-break space nonsense, no need to explain the name to others [03:23] well rak u too [03:23] <3 [03:23] :) [03:25] And here we go, people started kidding on the new name. OMG... :D [03:26] vrurg: btw notandthen is the first item here: https://github.com/perl6/problem-solving/issues/64 [03:27] AlexDaniel: aha, and there too. [03:29] Oh, and roast rename... Though I would leave it as is. rakus-spec sounds cumbersome. [03:29] vrurg: once I have a bit more time in a week I'll start figuring out what to do with the github org [03:30] vrurg: but if we're moving perl6/roast to rakulang or, then I'd much rather move it to something better like rakulang/spec [03:30] vrurg: even if it remains being “roast” [03:31] … or should it be /raku-spec ? ok now I don't know :) [03:31] AlexDaniel: it'd be confusing to people then. Project name better be consistent to the repo [03:31] Just 'spec' is no good. [03:32] vrurg: it doesn't even mention “roast” anywhere in the readme [03:33] so I don't think it'll be more confusing than it is now :) [03:33] It's in announces and release-guide. Not to mention unicode-generated-tests and New-Release-Policy [03:33] mmm that's true [03:34] anyway, I'm not sure, but point is that if repos are moving we can as well consistify and make them better [03:34] for example, that is *definitely* moving to something with a different name: https://github.com/perl6/specs/ [03:35] this, I mean [03:35] “and the "specs" in the repository name of the design documents tends to mean "speculations" now” [03:36] mental gymnastics instead of fixing the issue :) [03:36] That repo is likely to become something like 'historical-docs' [03:37] They still serve a good source of design resoning. I use them to find out why something was implemented this or that way. [03:37] old-design-docs ? :) [03:38] Anyway, we could expand ROAST abbreviation to something more meaningful. 'R' will stand for Raku, apparently. [03:38] AlexDaniel: either 'original-design-docs' or 'historical-design-docs' [03:39] we'll figure it out [03:40] ROAST: Raku Official ... Set of Tests? :) [03:42] Anyway, it was once proposed to reconsider roast structure because basing it on SNN is really confusing for people not historically involved (it took me half a year to realize the link between the old specs and directories). [03:42] yeah, it is confusing [03:43] * vrurg added an item on my Roast TODO list [03:46] you mean RakuSpec TODO list [03:46] :D [03:47] ok just kidding :) [03:47] Back to the label thing... 6e-release label would be needed, as well as labels for any future language versions. [03:47] Oh, let's bikeshed! Such a fun! :D :D :D [03:49] vrurg: speaking of bikeshedding, my proposal is to have 6.e mean just e [03:49] vrurg: last time there was a very long discussion on what D is going to be [03:50] AlexDaniel: I basically like it. But technically... We have too many changes related to the renaming to introduce another one without extra need. [03:51] I'd use `Raku E` in papers and media. But stick to `use v6.e` until the next release, perhaps. [03:51] We could even consider switching to all-numeric versioning, but that would likely mean jumping over to 7.x [03:53] But, again, not before 6.e. [03:57] yeah, that's ok [03:58] I think Raku 6.e is more correct in media, even if it does contain a little bit of Perl 6 in it [04:04] A problem-solving would be needed on this around this Jan/Feb, after we sort out most of the renaming problems. [04:05] And people need to cool down because it could turn into another round of hot discussions. [04:09] * vrurg is afk& [06:10] *** jmerelo joined [06:28] *** sena_kun joined [07:18] *** sena_kun left [07:33] *** jmerelo left [07:57] *** ufobat joined [08:40] *** sena_kun joined [09:08] *** sena_kun left [09:28] *** maettu joined [10:20] *** sena_kun joined [10:29] <|Tux|> Rakudo version 2019.07.1-454-g7e7aa2626 - MoarVM version 2019.07.1-313-g836396c74 [10:29] <|Tux|> csv-test-xs-20 0.429 - 0.439 [10:29] <|Tux|> csv-ip5xs 0.707 - 0.765 [10:29] <|Tux|> test-t --race 0.850 - 0.908 [10:29] <|Tux|> test-t 1.747 - 1.767 [10:29] <|Tux|> test 5.954 - 6.211 [10:29] <|Tux|> csv-ip5xs-20 6.329 - 6.366 [10:29] <|Tux|> test-t-20 --race 9.047 - 9.371 [10:29] <|Tux|> csv-parser 21.450 - 21.638 [10:29] <|Tux|> test-t-20 27.157 - 29.223 [10:50] *** Guest13443 joined [11:43] *** Altai-man_ joined [11:45] *** sena_kun left [11:55] *** ggoebel joined [12:03] *** |Tux| joined [13:12] ¦ Blin: nxadm++ created pull request #14: Merge nxadm/raku-blin-docker [13:12] ¦ Blin: review: https://github.com/perl6/Blin/pull/14 [13:31] Speaking of hot discussions: I really don't want to rename roast stuff away from the current SNN. Having trouble knowing the meaning is rectified with more questioning and docs. The synopses are too valuable to hide away under yet another layer of indirection. we don't have enough documentation for new developers as it is, renaming to confuse current folks doesn't help the cause IMHO. [13:44] *** sena_kun joined [13:46] *** Altai-man_ left [14:15] ¦ Blin: nxadm++ created pull request #15: migration from nxadm/raku-blin-docker [14:15] ¦ Blin: review: https://github.com/perl6/Blin/pull/15 [14:34] *** lucasb joined [14:36] *** ggoebel left [15:27] One more comment ref roast and SNN "speculations": there are still NYI design features listed in them, at least in S26 (Documentation), so there is still Perl-covered gold there that hasn't been fully mined. [15:34] tbrowder: making them 'historical' doesn't mean they won't be a good source of information. [15:38] i know, but, to me, using the term "speculations" for the original design docs has always had a bad connotation that might give new folks the wrong idea of them. [15:44] *** Altai-man_ joined [15:45] *** sena_kun left [15:46] *** ggoebel joined [15:49] *** Altai-man_ is now known as sena_kun [15:52] AlexDaniel: i got some info from git folks on upcoming integrated CI testing with git actions that you've probably seen . they are taking sign-ups for beta testing. 2000 free minutes/month for open source, excess minutes over 2000 per month for linux, win, mac, respectively: $0.008, $0.016, $0.08. [15:56] the beta requires agreeing to an NDA (non-disclosure agreement). the link also mentions free overtime for self hosting (coming soon, no mention of cost). [16:06] checking travis... [16:21] ¦ nqp/truffle: fb8237944d | (Paweł Murias)++ | src/vm/jvm/Truffle.nqp [16:21] ¦ nqp/truffle: [truffle] Remove the unusued :side_effects argument when adding nodes [16:21] ¦ nqp/truffle: [16:21] ¦ nqp/truffle: We are not using this when emitting AST for the truffle backend [16:21] ¦ nqp/truffle: review: https://github.com/perl6/nqp/commit/fb8237944d [16:21] ¦ nqp/truffle: 0dc156cc02 | (Paweł Murias)++ | 2 files [16:21] ¦ nqp/truffle: [truffle] Implement nqp::setmethcache [16:21] ¦ nqp/truffle: review: https://github.com/perl6/nqp/commit/0dc156cc02 [16:24] *** moon_child left [16:30] *** moon-child joined [16:32] *** moon-child left [16:32] *** moon-child joined [16:34] *** Kaiepi joined [16:35] *** Kaiepi left [16:35] *** Kaeipi joined [16:39] *** Merfont joined [16:40] *** Kaeipi left [17:06] tbrowder: I am in the beta, but I haven't tested yet. Spent quite some time getting to learn Travis. However, travis has been quite flakey lately [17:09] AlexDaniel: I sent a PR with the Docker changes to Blin [17:32] *** cognominal joined [17:43] *** Altai-man_ joined [17:45] *** sena_kun left [18:16] *** Merfont is now known as Kaiepi [18:17] when i need to use an array with REPR VMArray, is there a class that already exists that i can use or do i need to make my own? [18:19] this is for something in src/core.c, so i'm not sure if NQPArray can be used or not [18:25] Kaiepi: grep comes back with class array from native_array.pm6 [18:27] idt that can be used without being parameterized, and it doesn't let me parameterize it with Mu [18:28] there's IterationBuffer though, is that meant to be used in cases like this? [18:29] I think the starting comment in IterationBuffer could provide you with more information than I can. [18:32] looks like it'll work for this [18:32] thanks [18:49] El_Che: I did approve your request to use travis [18:52] El_Che: btw it could've been a merge of two repos (with two separate starting commits) [18:53] El_Che: though there's probably no good reason for doing it that way besides “because we can” :D [18:54] ¦ Blin: 0d09f2eb11 | (Claudio Ramirez)++ | 9 files [18:54] ¦ Blin: migration from nxadm/raku-blin-docker [18:54] ¦ Blin: review: https://github.com/perl6/Blin/commit/0d09f2eb11 [18:54] ¦ Blin: 0b12bc0b33 | (Aleks-Daniel Jakimenko-Aleksejev)++ (committed using GitHub Web editor) | 9 files [18:54] ¦ Blin: Merge pull request #15 from nxadm/master [18:54] ¦ Blin: [18:54] ¦ Blin: migration from nxadm/raku-blin-docker [18:54] ¦ Blin: review: https://github.com/perl6/Blin/commit/0b12bc0b33 [19:03] AlexDaniel: no, the travis thing was intentional :) [19:04] right? That's why I approved it? :) [19:09] *** jmerelo joined [19:12] AlexDaniel: master pushes will end in docker hub with :latest, version tags (eg, v1.0.1) will end up as :version (e.g. :1.0.1) [19:13] Sometimes the travis build fails because the Digest module is more than 10 minutes without output [19:13] Not always, though [19:14] I added --verbose to zef, and it helped somewhat, but maybe we need to go for --debug [19:23] ¦ rakudo/ugexe-patch-1: 2c5c013558 | (Nick Logan)++ (committed using GitHub Web editor) | .github/FUNDING.yml [19:23] ¦ rakudo/ugexe-patch-1: Create FUNDING.yml [19:23] ¦ rakudo/ugexe-patch-1: review: https://github.com/rakudo/rakudo/commit/2c5c013558 [19:23] If you've checked enough https://docs-stage.perl6.org, I'll replicate it in docs.perl6.org. [19:23] 2019-11-03T17:47:13Z #raku jmerelo: it looks like https://docs.raku.org isn't building, picking up updates [19:23] hey jmerelo, you have a message: https://gist.github.com/18ab103689fdd01aba16bc5769bd7625 [19:24] .tell cfa it's done by hand for the time being. Automatic deployment is yet to come... [19:24] jmerelo, I'll pass your message to cfa [19:24] ¦ rakudo: ugexe++ created pull request #3277: Create FUNDING.yml [19:24] ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/3277 [19:25] .tell rba whatever is the best for you. The docs*.perl6.org are only going to be temporary. [19:25] jmerelo, I'll pass your message to rba [19:32] ¦ rakudo: 2c5c013558 | (Nick Logan)++ (committed using GitHub Web editor) | .github/FUNDING.yml [19:32] ¦ rakudo: Create FUNDING.yml [19:32] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/2c5c013558 [19:32] ¦ rakudo: 3802cdfcad | (Aleks-Daniel Jakimenko-Aleksejev)++ (committed using GitHub Web editor) | .github/FUNDING.yml [19:32] ¦ rakudo: Merge pull request #3277 from rakudo/ugexe-patch-1 [19:32] ¦ rakudo: [19:32] ¦ rakudo: Create FUNDING.yml [19:32] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/3802cdfcad [19:33] AlexDaniel: Can you enable this in Travis? https://travis-ci.org/perl6/Blin [19:33] (or give me access?) [19:33] “This is not an active repository You don't have sufficient rights to enable this repo on Travis. Please contact the admin to enable it or to receive admin rights yourself” [19:34] what the? :) [19:35] ¦ rakudo: 1ec69e1f6a | tony-o++ (committed using GitHub Web editor) | .github/FUNDING.yml [19:35] ¦ rakudo: Add to yaml as GH approves more folks. [19:35] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/1ec69e1f6a [19:35] AlexDaniel: maybe add travis here: https://github.com/perl6/Blin/settings [19:36] El_Che: yeah [19:37] El_Che: is it better now? [19:37] I hope I didn't break anything… [19:38] Now go here: https://travis-ci.org/account/repositories and enable Blin [19:42] El_Che: there's no such repo O_o [19:43] El_Che: I think I can do that. [19:43] AlexDaniel: whut?? I see it [19:43] ah, wrong tab [19:43] and I have the switch to enable it [19:43] enabled! [19:43] (but no rights to do it :) ) [19:43] great job :) [19:44] just triggered a build [19:44] https://travis-ci.org/perl6/Blin/builds/607306940 [19:44] El_Che: I just gave you admin rights to blin repo, if that helps [19:44] AlexDaniel: should not be needed now, travis seems ok [19:44] AlexDaniel: it's handy though to restart build [19:44] s [19:45] El_Che: I just gave requested permissions, I don't know if it was needed when I did it. [19:45] see above above Digest [19:45] anyway, what's that "perl6" org? Sounds old :) [19:45] *** Altai-man_ left [19:46] AlexDaniel: the renaming will be repo by repo, I understand [19:47] notable6: weekly [19:47] lizmat, 8 notes: https://gist.github.com/d40f2774d88e4999f7484c7ecb39b2c0 [19:48] *** jmerelo left [19:53] . [19:53] 2019-11-04T19:25:11Z #raku-dev rba whatever is the best for you. The docs*.perl6.org are only going to be temporary. [19:54] Hmm. Just missed jmerelo. [19:55] El_Che: re "new rakudo-pkg support (and packages) for new releases: ubuntu 19.10, Fedora 31, centos 8", should I use a specific link for that? [19:55] lizmat: maybe https://github.com/nxadm/rakudo-pkg#os-repositories ? [19:56] ok, thanks [19:56] notable6: weekly reset [19:56] lizmat, Moved existing notes to “weekly_2019-11-04T19:56:09Z” [19:56] I have specific link for each pkg, but is less desirable than a repo [19:56] eg https://nxadm.github.io/rakudo-pkg/latest-release.html?os=fedora&version=31&arch=x86_64 [19:59] Regarding the downloads page on rakudo.org. Should we promote as well the rakudo releases? At the moment you will find only the rakudo star releases. [20:00] May we link to the pkgs from El_Che too? [20:05] i thought we already did [20:13] *** ufobat_ joined [20:17] *** ufobat left [20:18] MasterDuke: I am not a fan of the download page: [20:18] - Rakudo Star [20:18] - Installing from binaries [20:18] - Installing from source [20:18] - [20:18] Rakudo Star 2019.03 Errata [20:18] (whut?) [20:19] and another Rakudo Weekly hits the Net: https://rakudoweekly.blog/2019/11/04/2019-44-comma-cro/ [20:20] Star on top and at the bottom, and references to old releases while rakudo is more recent [20:20] <[Coke]> Is the problem that the rakudo star release is behind? [20:21] no, the problem is that unrelated things are mashed together [20:21] 1. Star 2. Binaries 3. Source 4. Star errata [20:22] 2nd problem is that the impression is created that the latest star release corresponds with the latest rakudo release [20:25] ha, github/stripe requires a utility bill or bank statement with your address on it [20:26] which I can't provide, I don't have that, I'm not even sure what they are asking for :D [20:26] like, maybe in some countries you do receive papers where your address is specified? [20:30] yeah, but even if we don't actually get it in the mail you usually can see a statement online that you could print out [20:37] it doesn't have my address in it [20:39] I'm not even sure if you're required to have an address at all [20:39] given e-residency and stuff like that [20:42] * [Coke] hasn't had to provide proof of address except for getting other forms of ID, like a new york state driver's license. [20:42] <[Coke]> (and then that could be used to get a passport, etc.) [20:43] I did submit a pdf of a page from the government website, which does have my address listed, but doesn't have a date or signature/stamp of any sort [20:43] <[Coke]> mm, doesn't sound super verifiable. :) [20:43] * MasterDuke has had to a couple times recently (e.g., to get driver's license realid certified, to sign up for nhs) [20:44] I know one way to do it, which is to request a document from the population registry [20:45] but it's an annoying process [20:57] i'm trying to pass a BOOTHash for named type parameters as the last element in the list of parameters for nqp::parameterizetype for a role, but fsr it's turning into a normal Hash when it gets assigned to %named in Metamodel::ParametricRoleGroupHOW!produce_parameterization, which makes it throw and doesn't happen when you parameterize by other means [20:57] what do i need to do to make it stay a BOOTHash? [21:04] I haven't ran the tests locally yet, but gitlab-ci says these should be OK (apart from kernel signals): https://dist.tyil.nl/raku/rakudo-star/ [21:04] if anyone wants to do a test run on them or check other things, please do [21:05] tyil++ [21:05] I would like to get stuff fixed where possible, so I can do a proper release for 2019.10 later this month [21:05] I'll contact the guy that builds the .msi package as well, to see if he can get the Windows installers to work as well [21:05] Kaiepi: I would guess it became a Hash before binding to %named. [21:06] I have enabled sponsorships in doc, roast, nqp, moarvm [21:06] so feel free to, I guess [21:06] Kaiepi: most likely it happens when you pass it to nqp::parameterizetype. [21:07] the system is kinda weird because you have to do it in every repo separately [21:08] *** travis-ci joined [21:08] Rakudo build failed. tony-o 'Add to yaml as GH approves more folks.' [21:08] https://travis-ci.org/rakudo/rakudo/builds/607303410 https://github.com/rakudo/rakudo/compare/3802cdfcad6f...1ec69e1f6a81 [21:08] *** travis-ci left [21:10] restarted the one failing job [21:20] hmm, Linenoise fails to install for me with rakudo-star-2019.07.1 [21:21] [Linenoise] Failed to open file /home/tyil/projects/personal/rakudo-star/work/build/rakudo-star-2019.07.1/modules/Linenoise/lib/Linenoise.pm6: No such file or directory [21:21] <[Coke]> AlexDaniel: any idea how to become a sponsor? [21:21] [Coke]: try starting from here? https://github.com/sponsors [21:22] [Coke]: I think once you have it set up, you go here: https://github.com/sponsors [21:22] [Coke]: and click the sponsor button, then choose the dev you want to sponsor [21:23] <[Coke]> That's to become a sponsored person, isn't it? [21:24] [Coke]: the rakudo repo now has a "Sponsor" button at the top [21:24] <[Coke]> the "join the waitlist" buttons seem to be for if I want to get money, not give it. [21:24] [Coke]: I think it's both, I just clicked “Select” on one of the tiers and it worked [21:24] e.g. here https://github.com/sponsors/ugexe [21:25] it could be that you don't even need to set anything up [21:25] <[Coke]> ok. You said you had set it up on doc, but didn't see a sponsor button there; I *do* see it on rakudo, though. Thank you! [21:28] right. So which is it? You just go straight to selecting a tier and that's it? [21:35] <[Coke]> I clicked on the sponsor link on the project, and from there can pick a person to sponsor. [21:38] ok! [21:43] m: my IterationBuffer:D $list := nqp::create(IterationBuffer); $list.push: nqp::hash(); say $list[0].^name [21:43] rakudo-moar 1ec69e1f6: OUTPUT: «5===SORRY!5=== Error while compiling ␤Could not find nqp::create, did you forget 'use nqp;' ?␤at :1␤------> 3:D $list := nqp::create(IterationBuffer)7⏏5; $list.push: nqp::hash(); say $list[0].␤» [21:43] m: use nqp; my IterationBuffer:D $list := nqp::create(IterationBuffer); $list.push: nqp::hash(); say $list[0].^name [21:43] rakudo-moar 1ec69e1f6: OUTPUT: «Hash␤» [21:43] Can the sponsors beeing setup for an org too? Do I alway have to choose individual developers? [21:44] *** lucasb left [21:44] so that's how that was happening vrurg [21:44] rba: yeah, it's weird. I don't see a way to sponsor an org or a repo [21:44] rba: so it's “sponsor a dev”, you just choose a person [21:45] m: use nqp; class NativeArray is repr { }; my NativeArray:D $list := nqp::create(NativeArray); nqp::push($list, nqp::hash()); say nqp::atpos($list, 0).^name [21:45] How do you get the money then? Do I have to tell them my bank account? [21:45] rakudo-moar 1ec69e1f6: OUTPUT: «BOOTHash␤» [21:45] so ig i can't use IterationBuffer for this [21:45] rba: yep, each dev can define tiers (like 1$ a month, 5$ a month, etc.), and you pay for it [21:47] also, “GitHub will match your sponsorship”, at least in some cases [21:58] ah, I think it's possible to configure project sponsoring [21:59] we'd just need a single rakudo account somewhere, like CommunityBridge maybe? [22:00] rba: check this out: https://help.github.com/en/github/building-a-strong-community/displaying-a-sponsor-button-in-your-repository [22:04] <[Coke]> annoying you can only have 4 devs. [22:32] ¦ rakudo: 654d6a1693 | (Tom Browder)++ (committed using GitHub Web editor) | docs/rakudo-nqp-and-pod-notes.md [22:32] ¦ rakudo: Correct formatting error [22:32] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/654d6a1693 [22:36] ¦ rakudo: aa06d32abc | (Tom Browder)++ (committed using GitHub Web editor) | docs/rakudo-nqp-and-pod-notes.md [22:36] ¦ rakudo: Change IRC name to #raku-dev [22:36] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/aa06d32abc [22:38] ¦ rakudo: 044b339024 | (Tom Browder)++ (committed using GitHub Web editor) | docs/rakudo-nqp-and-pod-notes.md [22:38] ¦ rakudo: More Raku entries [22:38] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/044b339024 [23:00] *** AlexDaniel left [23:22] Kaiepi: what if you add 'is raw' to IterationBuffer push var parameter? Basically, this is where you get nqp::hash() hllized itnto Hash, as it looks to me. [23:25] i think a mirrored R and another R together could be stylized into a butterfly [23:31] m: use nqp; my IterationBuffer:D $list := nqp::create(IterationBuffer); nqp::push($list, nqp::hash()); say nqp::atpos($list,0).^name [23:31] rakudo-moar 044b33902: OUTPUT: «BOOTHash␤» [23:31] Kaiepi: ^^^ [23:32] hold on, i'm waiting on rakudo to build [23:34] Kaiepi: Anyway, the biggest problem is [] because it falls back to AT-POS method. But methods don't support `is raw` in return values. This is where you'd always have your BOOTHash hllized. [23:34] Use of nqp::atpos is inevitable anyway. [23:34] ah, ok [23:35] And I have recompiled already. `is raw` doesn't help with the parameter. You're bound to nqp::push / nqp::atpos. [23:35] Wether it makes sense using IterationBuffer is very much doubtful then.