[00:27] *** titsuki left [00:45] *** sena_kun left [00:59] *** sena_kun joined [02:45] *** sena_kun left [02:59] *** sena_kun joined [04:46] *** sena_kun left [05:01] *** sena_kun joined [05:06] * sjn is getting some build warnings when compiling 2020.01 [05:07] src/core/interp.c: In function ‘MVM_interp_run’ [05:08] hm. moarvm warnings... [06:12] sjn: yep I've seen these too [06:13] I typically don't complain because I'm on the latest gcc which tends to have more warnings for everything, but others won't see them [06:25] hi. in rakudo?src/core.c/Bool.pm6 I read "These operators are normally handled as macros in the compiler" [06:26] where can I find these macros' definition ? [06:40] hum I guess I found them [06:45] *** sena_kun left [07:01] *** sena_kun joined [07:06] *** AlexDaniel left [07:11] *** AlexDaniel joined [07:12] *** AlexDaniel left [07:12] *** AlexDaniel joined [07:50] *** stoned75 left [08:23] *** domidumont joined [08:45] *** sena_kun left [09:01] *** sena_kun joined [09:12] is it just me or 2020.01 has visibly longer build time? Parse stage is usually 50-52 seconds for me, but last night it was 67, which is not really cool. I wonder if it's my system issue or. [09:42] Files=1301, Tests=109816, 212 wallclock secs (28.20 usr 8.12 sys + 2948.93 cusr 271.94 csys = 3257.19 CPU) [09:44] .ask [Coke] there is hardly anything in Perl.pod6 anymore? [09:44] lizmat, I'll pass your message to [Coke] [09:45] . [10:08] *** AlexDaniel left [10:09] *** squashable6 left [10:10] *** squashable6 joined [10:11] ¦ nqp: 7e0ac3da16 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION [10:11] ¦ nqp: Bump NQP to get IPNS changes [10:11] ¦ nqp: review: https://github.com/perl6/nqp/commit/7e0ac3da16 [10:11] ¦ rakudo/master: 4 commits pushed by (Ben Davies)++, (Elizabeth Mattijsen)++ [10:11] ¦ rakudo/master: 7c7d3b96a7 | Support basic usage of UNIX sockets over TCP with IO::Socket::INET [10:11] ¦ rakudo/master: 1a5b2185a9 | Add constant for PF_UNSPEC [10:11] ¦ rakudo/master: ed4226d761 | Add a family named parameter to IO::Socket::INET.connect and .listen [10:11] ¦ rakudo/master: 547c7b94e5 | Merge pull request #3357 from Kaiepi/unix [10:11] ¦ rakudo/master: review: https://github.com/rakudo/rakudo/compare/0d530092fade...547c7b94e518 [10:13] .ask tyil please let me know how I can help to get a Rakudo Star 2020.01 out before FOSDEM :-) [10:13] lizmat, I'll pass your message to tyil [10:14] lizmat: I'm currently contemplating to make just a rakudo-star 2020.1 source-only release (so no .msi, no .dmg) if I get no response from the official maintainers before FOSDEM [10:15] I can start preparations on it, but I can't make a guarantee it'll be done before FOSDEM hits :( [10:15] there are no guarantees in life :-) [10:15] ++tyil for starting preps [10:36] ¦ rakudo: bae5fc7d49 | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION [10:36] ¦ rakudo: Bump NQP to get Moar support for IP6NS changes [10:36] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/bae5fc7d49 [10:37] sena_kun Kaiepi ^^ [10:45] *** sena_kun left [11:00] *** sena_kun joined [11:20] *** Guest78373 joined [11:26] *** Guest78373 left [11:27] *** Guest48371 joined [11:34] *** Guest48371 left [11:37] we have a looot of PRs [11:38] *** dogbert1 joined [11:42] ¦ rakudo: bd68955b76 | (Ben Davies)++ | src/core.c/Parameter.pm6 [11:42] ¦ rakudo: Add Parameter.prefix and Parameter.suffix [11:42] ¦ rakudo: [11:42] ¦ rakudo: The prefix method returns the *, **, or + markers a parameter was [11:42] ¦ rakudo: declared with, if any, and the suffix method returns the ? or ! [11:42] ¦ rakudo: marker a parameter was declared with, if any. [11:42] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/bd68955b76 [11:42] ¦ rakudo: 3f6a2a2225 | (Ben Davies)++ | src/core.c/Parameter.pm6 [11:42] ¦ rakudo: Refactor Parameter.raku and improve how it handles parameter names [11:42] ¦ rakudo: [11:43] ¦ rakudo: Parameter.raku was pretty complex and prone to bugs, particularly with [11:43] ¦ rakudo: how it determined what name the parameter was declared with. Now that [11:43] ¦ rakudo: other methods can handle most of that work for this method, use them [11:43] ¦ rakudo: instead of reimplementing their behaviour. [11:43] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/3f6a2a2225 [11:43] ¦ rakudo: c9a6b02de2 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/Parameter.pm6 [11:43] ¦ rakudo: Merge pull request #3430 from Kaiepi/parameter-raku [11:43] ¦ rakudo: [11:43] ¦ rakudo: Simplify Parameter.raku, add Parameter.prefix and Parameter.suffix [11:43] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/c9a6b02de2 [11:44] ¦ rakudo: b2c809e4f3 | vendethiel++ | 2 files [11:44] ¦ rakudo: Make Parameter's BUILD use named args [11:44] ¦ rakudo: [11:44] ¦ rakudo: Between 3d3578 and d31fb2, the by-name marker has been lost. [11:44] ¦ rakudo: This commit restores it, allowing a Parameter to be constructed [11:44] ¦ rakudo: manually. [11:44] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/b2c809e4f3 [11:44] ¦ rakudo: 749ab904f2 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | t/02-rakudo/99-misc.t [11:44] ¦ rakudo: Merge pull request #3330 from vendethiel/manual-parameter-new [11:44] ¦ rakudo: [11:44] ¦ rakudo: Make Parameter's BUILD use named args [11:44] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/749ab904f2 [12:02] *** titsuki joined [12:05] clickbaits lizmat with https://github.com/perl6/nqp/pull/596 [12:05] 2020-01-26T18:09:58Z #raku-dev dogbert11 yes, a PR for 6d23891a3a7e https://github.com/perl6/nqp/issues/559 would be great! [12:05] (2020-01-03) https://github.com/perl6/roast/commit/6d23891a3a Some s/perl/raku changes [12:12] ¦ nqp: 9f3f0a530d | (Jan-Olof Hendig)++ | src/QRegex/Cursor.nqp [12:12] ¦ nqp: Fix for https://github.com/perl6/nqp/issues/559 [12:12] ¦ nqp: [12:12] ¦ nqp: During timtoady's cleanup of the Braid API a copy paste error made [12:12] ¦ nqp: it through. This was discovered by cognomial++ some time ago. [12:12] ¦ nqp: This commit fixes the error where the Braid grammar class attribute [12:12] ¦ nqp: should have been initialized with a grammar instance. [12:12] ¦ nqp: review: https://github.com/perl6/nqp/commit/9f3f0a530d [12:12] ¦ nqp: 75c01d8c70 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/QRegex/Cursor.nqp [12:12] ¦ nqp: Merge pull request #596 from dogbert17/fix-braid-init-copy-pasto [12:12] ¦ nqp: [12:12] ¦ nqp: Fix for https://github.com/perl6/nqp/issues/559 [12:12] ¦ nqp: review: https://github.com/perl6/nqp/commit/75c01d8c70 [12:16] lizmat++ [12:20] ¦ rakudo/master: 10 commits pushed by (Elizabeth Mattijsen)++ [12:20] ¦ rakudo/master: review: https://github.com/rakudo/rakudo/compare/749ab904f2b8...14abd58861ac [12:33] ¦ roast: e92bc17a24 | (Elizabeth Mattijsen)++ | S06-signature/introspection.t [12:33] ¦ roast: Fix test for unnamed named parameter in signature [12:33] ¦ roast: review: https://github.com/perl6/roast/commit/e92bc17a24 [12:46] *** sena_kun left [12:49] *** AlexDaniel joined [12:49] *** AlexDaniel left [12:49] *** AlexDaniel joined [12:51] *** patrickb joined [12:52] o/ [12:52] 2020-01-28T10:09:55Z #raku patrickb I am not territorials about packages. The more the merrier and even better if we can work together! [12:53] El_Che: Great! Then I'll give that a shot. [12:54] patrickb, I'll pass your message to El_Che [12:54] lizmat, tyil: I'll probably get 2020.01.1 precomp packages for mac/win/linux ready before fosdem starts (maybe I'll even manage to automate the process). [12:54] patrickb: for Star ? cool! [12:55] lizmat: No, not star. [12:55] ah, bummer :-) [12:55] Only rakudo + zef. [12:59] patrickb: nice work :D [13:00] *** sena_kun joined [13:02] weekly: please mention old-issue-tracker squashathon [13:02] AlexDaniel, Noted! (weekly) [13:02] weekly: #perl6 irc channel now forwards to #raku [13:02] AlexDaniel, Noted! (weekly) [13:02] by the way [13:03] I can't do it for #perl6-dev [13:03] so, whatever [13:05] AlexDaniel : *you* can't, or it can't be done ? [13:05] I can't [13:05] I asked for permissions but didn't get them [13:06] anyway, whoever has the founder flag can do it relatively easily [13:06] you just set the flags with mlock and possibly also turn the guard on [13:06] that's what I did for #perl6 and it should work fine [13:07] do you know who the founder flag has ? [13:11] jnthn, TimToady, masak, mst [13:11] I think jnthn tried to give it to me too but turns out the limit is 4 founders in total [13:14] I suggested we remove TimToady so that I can set the redirects, but that didn't happen :) [13:14] btw he is currently idling on #perl6-dev but not here [13:16] that's a very striking image :-( [13:17] jnthn: want me to guide you through the commands you need to run? [13:19] jnthn: /msg ChanServ set #perl6-dev guard on [13:19] jnthn: /msg ChanServ set #perl6-dev mlock +Cinptzf #raku-dev [13:19] I think [13:20] the important ones are +f and +i [13:21] the rest are just ones that are already there [13:22] and guard should make a bot join the channel so that it won't get fully empty [13:22] +i is what is going to make the redirect work (and you'll be able to invite yourself to that channel if you ever want to join it to see what's going on there) [13:23] as I've said, I have no idea what I'm doing so there's possibly a better way, but this is going to work too [13:26] * AlexDaniel sleep & [13:44] *** lucasb joined [13:45] <|Tux|> Rakudo version 2020.01-34-g14abd5886 - MoarVM version 2020.01.1-2-gcbb04d462 [13:45] <|Tux|> csv-test-xs-20 0.362 - 0.367 [13:45] <|Tux|> csv-ip5xs 0.690 - 0.733 [13:45] <|Tux|> test-t --race 0.780 - 0.795 [13:45] <|Tux|> test-t 1.803 - 1.823 [13:45] <|Tux|> csv-ip5xs-20 5.673 - 5.814 [13:45] <|Tux|> test 7.087 - 7.317 [13:45] <|Tux|> test-t-20 --race 8.869 - 8.877 [13:45] <|Tux|> csv-parser 23.149 - 23.623 [13:45] <|Tux|> test-t-20 28.891 - 29.618 [13:53] <[Coke]> (Perl6.pod) it's a class definition. With the latest changes made to xt/examples-compilation, I don't have an easy way to get the error on the compile, so I don't know what it's complaining about. [13:53] 2020-01-28T09:44:55Z #raku-dev [Coke] there is hardly anything in Perl.pod6 anymore? [13:54] <[Coke]> ^^ lizmat [13:54] will look in a mo [14:05] * [Coke] adds https://github.com/Raku/doc/issues/3188 [14:08] <[Coke]> lizmat: oh. OK, figured out the problem. :) [14:08] *phew* [14:09] <[Coke]> 1) I have a script that only runs xt/ against files changed since I last updated the git checkout. so it saw the class Perl is Raku ... on my slightly older perl6, this complained (presumably because it didn't know what Raku was) - then I rebuilt perl6 with git latest. re-ran the test. it failed. couldn't see why, if I tried to test it separately, the code worked. Turns out that the nqp::getcomp that you [14:09] <[Coke]> were asking about is in the examples compilation test file itself - so after rakudo update it was failing to find the compiler and failing because of that. [14:10] <[Coke]> updating the testing file... [14:10] aaaahh good catch! [14:11] <[Coke]> what's the new preferred way to getcomp? [14:12] the old one but with `Raku` instead of `perl6` [14:12] ? [14:12] <[Coke]> Yes, but there was a conditional to allow it to work on older versions. [14:12] <[Coke]> my $parser = nqp::getcomp('perl6') // nqp::getcomp('Raku'); ? [14:12] no, please use || [14:13] Brian Duggan found that // fails on older rakudo's :-( [14:13] <[Coke]> that did it (nqp obj. is too low level for ||) [14:13] for // or || ? [14:13] * sena_kun sent a bunch of PRs with `//` [14:13] yeah :-( [14:13] woah [14:14] bisectable6: use nqp; nqp::getcomp("Raku") // nqp::getcomp("perl6") [14:14] lizmat, Bisecting by exit code (old=2015.12 new=14abd58). Old exit code: 1 [14:14] lizmat, bisect log: https://gist.github.com/c8c94d2fe9d37831ff8de79cd7f7b854 [14:14] lizmat, (2020-01-24) https://github.com/rakudo/rakudo/commit/b787095358bcbac4c6326b99e9673e54ef5afd58 [14:14] bisectable6: use nqp; nqp::getcomp("Raku") || nqp::getcomp("perl6") [14:14] lizmat, On both starting points (old=2015.12 new=14abd58) the exit code is 0 and the output is identical as well [14:14] lizmat, Output on both points: «» [14:14] *sigh* [14:15] sorry sena_kun, messed up that one [14:15] <[Coke]> "//" failed for me in a very recent build [14:15] well, ones which were accepted can be accepted again [14:15] those which are not yet can be fixed [14:17] <[Coke]> ... which you may not have noticed if you were looking for Raku first. I happened to have perl6 first in my initial guess. [14:17] well, yeah... [14:19] so `nqp::getcomp('Raku') || nqp::getcomp('perl6');` is safe? [14:19] <[Coke]> I think so. if you do perl6 || Raku on a later version, it works. [14:20] yeah, that's what Brian Duggan found: https://github.com/bduggan/p6-jupyter-kernel/pull/54#issuecomment-579242473 [14:20] m: my $s = Str(123456789) for ^100_000; say now - INIT now [14:20] rakudo-moar 14abd5886: OUTPUT: «0.136214␤» [14:20] m: my $s = ~123456789 for ^100_000; say now - INIT now [14:20] rakudo-moar 14abd5886: OUTPUT: «0.0120425␤» [14:21] wow [14:21] * sena_kun updated patches [14:21] it's from rindolfs example yesterday [14:22] sena_kun++ [14:27] <[Coke]> m: my $s = 123456789.Str for ^100_000; say now - INIT now [14:27] rakudo-moar 14abd5886: OUTPUT: «0.03648555␤» [14:29] that last one is even more suspect [14:29] .Str should be the fastest? [14:29] as prefix:<~> calls that ? [14:35] A I misremembering, or did Pugs-era proto-Raku not have a "backwards" Range, e.g. a 3-element 5..3? [14:36] double negative, sorry... "didn't Pugs have such a Range"? [14:38] <[Coke]> you might be able to figure that out based on the last roast skips for pugs which were eventually removed. [14:38] [Coke]:good call [14:42] ¦ rakudo: d8e859d000 | (Elizabeth Mattijsen)++ | 3 files [14:42] ¦ rakudo: Make has Str $.a = 42 a compile time failure [14:42] ¦ rakudo: [14:42] ¦ rakudo: - adapts default BUILDPLAN logic to perform some type tests [14:42] ¦ rakudo: - adds X::TypeCheck::Attribute::Default class [14:42] ¦ rakudo: - adds X::TypeCheck::Attribute::Default stub for setting compilation [14:42] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/d8e859d000 [14:42] lizmat: https://gitlab.com/tyil/rakudo-star/pipelines/112963099 perhaps it'll just work :> [14:42] m: .say for 10 ... 1 # TreyHarris [14:42] rakudo-moar 14abd5886: OUTPUT: «10␤9␤8␤7␤6␤5␤4␤3␤2␤1␤» [14:43] this is actually statically optimized [14:43] m: .say for ^10 .reverse # as is this, if I recall correctly [14:43] rakudo-moar 14abd5886: OUTPUT: «9␤8␤7␤6␤5␤4␤3␤2␤1␤0␤» [14:45] *** sena_kun left [14:46] ¦ roast: 218eae0a44 | (Elizabeth Mattijsen)++ | APPENDICES/A02-some-day-maybe/misc.t [14:46] ¦ roast: Typecheck on default value for attribute changed [14:46] ¦ roast: [14:46] ¦ roast: with https://github.com/rakudo/rakudo/commit/d8e859d000 [14:46] ¦ roast: review: https://github.com/perl6/roast/commit/218eae0a44 [14:47] *** |Tux| left [14:51] lizmat: ~ seems to be the fastest [14:51] * lizmat wonders why [14:51] and why is Str() so slow, does it do a lot of extra stuff [14:52] --profile ? [14:53] I did profile yesterday and noticed that when using Str() 10% of the code was interpreted while 0% was interpreted when using ~ [14:53] lizmat: yes, but ... is a Seq constructor, not a Range constructor [14:54] here's the code from yesterday: https://gist.github.com/dogbert17/9e039d6af26a09e144f144b4e0aba220 [14:54] indeed... but that case is actually optimized [14:54] *** |Tux| joined [14:54] TreyHarris: there is no other syntax for reverse ranges, afaik [14:55] lizmat: understood. If you killfiled todd&margo you may not understand why I'm zooming in on this particular case of Range rather than the pragmatics [14:56] indeed I have and indeed I haven't [14:56] :-) [14:57] Yeah--well, I was trying to explain why "my Int $x; $x.Range" produces something and "my Int $x = 3; $x.Range" fails [14:57] yeah... people who want to know answers but are unwilling to teach themselves basics, will never understand that [14:58] I did notice something that may be a doc error? class Range says for .elems: "Returns Inf if either end point was specified as Inf or *." But it doesn't, it fails for being called on a lazy range. [15:00] And that wording seems wrong, it seems like if it does work on calculable lazy's it should return Inf if the right-hand is Inf, or zero if the left-hand is Inf (but the right-hand is not Inf) [15:00] that's probably a bug [15:00] I feel the doc is correct [15:00] bisectable6: dd ^Inf .elems [15:00] *** sena_kun joined [15:00] lizmat, Bisecting by output (old=2015.12 new=d8e859d) because on both starting points the exit code is 0 [15:01] I don't think .elems ever returns Inf these days [15:01] lizmat, bisect log: https://gist.github.com/731edfbffd86ada516b815d9d9faf40f [15:01] lizmat, (2017-06-07) https://github.com/rakudo/rakudo/commit/20310d7dcdd5cd877fc7bd46ad7a84f715bf1503 [15:01] lizmat:even to my suggestion that (Inf..3).elems should be 0, not Inf? [15:01] ah, I see that it was changed on purpose, so I guess it's a doc issue [15:02] Okay [15:02] Yeah, my recollection is that .elems should always return an Int or a Failure [15:02] Inf..3 should almost certianly say 0 elems though [15:02] m: say (Inf..3).elems [15:02] rakudo-moar d8e859d00: OUTPUT: «0␤» [15:02] Arguably the lhs > rhs => 0 check should come first [15:02] yeah [15:02] And it does :) [15:02] huh [15:02] m: dd Inf ~~ Int [15:02] rakudo-moar d8e859d00: OUTPUT: «Bool::False␤» [15:03] jnthn: ah-hah, i typoe'd. Good. [15:04] Phew, a bug we don't have. :) [15:04] In that case it's purely a doc issue [15:06] on R*: https://gitlab.com/tyil/rakudo-star/-/jobs/417548433 seems like it builds fine [15:06] (2020.01-rc1) [15:07] the spectest takes almost 1 hour, if it doesn't fail too much, I'll be able to publish 2020.01-rc1 on dist.tyil.nl before I sleep [15:07] m: say (*..3).elems [15:07] rakudo-moar d8e859d00: OUTPUT: «Cannot .elems a lazy list␤ in block at line 1␤␤» [15:07] ¦ roast: 8db6dba6af | (Elizabeth Mattijsen)++ | S12-attributes/smiley.t [15:07] ¦ roast: Typecheck on default value for attribute changed [15:07] ¦ roast: [15:07] ¦ roast: with https://github.com/rakudo/rakudo/commit/d8e859d000 [15:07] ¦ roast: review: https://github.com/perl6/roast/commit/8db6dba6af [15:08] tyil++ [15:09] m: say(∞..3).elems [15:09] rakudo-moar d8e859d00: OUTPUT: «Inf..3␤» [15:09] I'm fixing the docs for elems now [15:09] m: say(Inf..3).elems [15:09] rakudo-moar d8e859d00: OUTPUT: «Inf..3␤» [15:09] m: say((Inf..3).elems) [15:09] rakudo-moar d8e859d00: OUTPUT: «0␤» [15:09] m: say((∞..3).elems) [15:09] rakudo-moar d8e859d00: OUTPUT: «0␤» [15:13] afk for a few hours& [15:22] Huh, to make my editor happy, I had to blow away and recreate my doc repo from scratch under the Raku org rather than via the perl6 redirect. Now I'm getting permission denied on push via SSH key. my remote push url is origin `ssh://git@github.com/Raku/doc.git (push)` and I also tried it without the `.git`. [15:22] Anyone know what might be going on? [15:22] new public keys ? [15:22] No, before I got that error, it made me go through the "re-approve your public key" rigamarole, and I did that [15:23] then I have no idea :-( [15:23] really afk& [15:23] <[Coke]> is there extra debug output you can see from the command line? [15:27] Yes: `Pushing to ssh://git@github.com/Raku/doc.git␤ERROR: Permission to Raku/doc.git denied to treyharris.␤fatal: Could not read from remote repository.␤␤Please make sure you have the correct access rights␤and the repository exists.␤` [15:27] hmm, 'read'. let me do a fetch [15:27] Nope, fetch worked, push still fails [15:29] tfw local installation seems to work for rakudo-star-2020.01-rc1 [15:30] spectest at gitlab so far only failed for t/spec/S02-magicals/KERNEL.rakudo.moar, which it did last time as well [15:30] An ssh -T [email@hidden.address] works fine, so it's not my keys [15:33] <[Coke]> TreyHarris: what's your github id? [15:33] [Coke]: treyharris [15:34] I thought I'd pushed since the switch to the Raku org, but it's possible I haven't yet [15:34] If access wasn't copied over wholesale, maybe mine wasn't? [15:34] <[Coke]> I don't see you in the explicit list. perhaps you're under the "Raku" team, but I don't have rights to see that. [15:35] [Coke]: do you have rights to add me? [15:35] I have rights to close issues in any Raku-org repo, so I figured I was set [15:35] <[Coke]> ah, I can see it. you're not on the team. [15:35] weird [15:36] <[Coke]> er. I think? [15:36] Could you add me? Since I was going to move the emacs mode over soon, I'll need full org access like I had on perl6 [15:36] s/had/have/ [15:38] <[Coke]> I'm not on IRC much these days: can someone say "yes that's cool"? [15:40] yes that's cool [15:40] (I'm not sure what it's about tho) [15:43] [Coke]: if you look, you'll see I've been a member of the org admins of perl6 forever, so I'm safe ;-) [15:43] https://github.com/orgs/perl6/teams?query=%40treyharris [15:43] <[Coke]> ok, you seem trustworthy. :) [15:44] :-) [15:44] lmk when I can try pushing again [15:44] <[Coke]> ok, you should have an invite. [15:44] Okay [15:44] <[Coke]> probably have to click a button before you can push [15:47] [Coke]: oh, d'oh... Alex~~Daniel (not mentioning him to trigger spurious notifications) added me 27 days ago--but the button didn't appear until I hit reload just now (following your re-invitation, I assume). Must've been one of those "if you miss it the first time, you have to go a specific place to see it again" [15:47] <[Coke]> weird. I would have expected to find your name with a "invite sent" next to it. thought I saw that on others. [15:47] <[Coke]> welcome aboard. [15:51] .tell AlexDaniel I'll need full access to the Raku org on GitHub to move the emacs mode repo over and get the package's canonicity validated so Emacs package managers will accept it as a valid redirect. I was a member of Org Admins for perl6 forever so I'm relatively trustworthy ;-) Send me a privmsg if you need to discuss further [15:51] TreyHarris, I'll pass your message to AlexDaniel [15:51] oops, mentioned him there, didn't I? Hope I don't wake him [15:53] You can't privmsg tellable6, looks like. Maybe I'll drop an issue in whateverable for rout-tuit time [15:58] Appreciate a quick double-check of https://github.com/Raku/doc/commit/2c083530bc for correctness from those of you paying attention to this Range thing [16:03] .tell lizmat https://gitlab.com/tyil/rakudo-star/-/jobs/417548439#L1370 not sure how bad this is [16:03] tyil, I'll pass your message to lizmat [16:11] tyil: I keep trying to parse 'tyil' as a 'itym'~'til'~'ty' mashup :-) [16:12] just type t, press tab and hope for the best [16:12] :D [16:12] tellable6: okay i will [16:12] TreyHarris, I haven't seen okay around, did you mean oka_? [16:12] ;-) [16:12] haha [16:15] turns out tellable already strips out some things, so it should be possible to: [16:15] .tell ty_il I think you can do this [16:15] TreyHarris, I'll pass your message to tyil [16:15] wah [16:15] why does that work [16:15] albeit not completelyu [16:17] Oh, the code I thought would serve this purpose is only called in the output end, not the noticing-a-nick-is-active end. So no. Underscores are allowed in nicks, though, so I'm not sure why that part of the regex is there: https://github.com/Raku/whateverable/blob/63df823cfdb058a319b7214dd48aaad51319508a/xbin/Tellable.p6#L41 [16:18] hrm, actually I don't see why it wouldn't have told you, tyil, unless it doesn't tell until you've gone inactive first? [16:19] what does it count as inactive? [16:19] because I get the tell updates usually without having to disconnect or anything [16:20] 10 minutes, it looks like: https://github.com/Raku/whateverable/blob/63df823cfdb058a319b7214dd48aaad51319508a/xbin/Tellable.p6#L31 [16:20] then I guess I'll get them at some point tonight [16:20] cycling home takes about 10 minutes, at least [16:22] hmm [16:22] ===> Install [FAIL] for DateTime::Format: ===SORRY!=== [16:22] finish_code_object [16:22] on rakudo-star-2020.01-rc1, after installing on desktop [16:26] . [16:26] hey AlexDaniel, you have a message: https://gist.github.com/d7f68dad4fdd8f11d10ca74246bde046 [16:27] dalman: Gah, I've now reached the point of cube-solving practice where there are a couple YouTube videos I watch with unsolved cubes in the background of the set, and on one I get twitchy that I can't solve it :-) The other is a prob with an impossible cube state, so that one bothers me in a totally different way... [16:27] oops, fat-fingered paste there [16:27] wrong channel [16:29] Odd, why did tellable6 turn my message to AlexDaniel into a gist? (And AlexDaniel, if you want to bed < 3 hours ago, I hope I wasn't the one who woke you!) [16:29] TreyHarris: see the graph on https://github.com/AlexDaniel/orgsleep [16:30] I had to receive groceries :) but it dooesn't really matter anyway [16:31] Ah-hah... do you do the "6 days a week" thing? [16:31] polyphasic sleeping, I meant--which is not 6 days a week, apparently. Been awhile since I looked at it [16:32] TreyHarris: it's unintentional :( [16:33] TreyHarris: https://en.wikipedia.org/wiki/Non-24-hour_sleep%E2%80%93wake_disorder [16:33] understood. that sucks--i had insomnia for months after 9/11 (I lived nearby and worked in the WTC until the week before) and it's the worst [16:33] TreyHarris: tellable6 is a relatively new bot so it's not perfect yet. The message was a bit too long so it gisted it :) [16:34] it adds extra text for the timestamp and stuff, so it's unavoidable. But the fixable thing is figuring out when exactly the message is too long [16:35] and honestly I don't know how to calculate that [16:35] last time I looked I didn't really understand [16:35] it depends on the… server you're on? Or something like that. It's weird [16:36] You could look at https://github.com/weechat/weechat/blob/d2dda92dafcf346d1a158f308e7f8fbfcc313281/src/plugins/irc/irc-message.c#L954 which is how WeeChat decides whether and how to split messages [16:37] oops, I meant https://github.com/weechat/weechat/blob/d2dda92dafcf346d1a158f308e7f8fbfcc313281/src/plugins/irc/irc-message.c#L983 -- I tried to scroll up to enclude that comment and insted scrolled up to the prior func [16:38] and I can't reed or spel very wele aparently... [16:40] <[Coke]> ooh, cuber. I got a teraminx for christmas. [16:41] TreyHarris: https://github.com/Raku/whateverable/issues/354#event-2986379714 [16:46] *** sena_kun left [16:46] TreyHarris: you should have all permissions in the world now :) [16:48] TreyHarris: I'm still trying to figure out the exact list of limitations on github for those who are not Owners [16:48] and yeah, github in that regard is very limited :( [16:48] they recently added triage and maintain levels so that's nice, but it's completely different [16:49] yeah--GitHub absolutely loves to make world-breaking changesets that, if you opt into any, you opt into all [16:51] TreyHarris: don't create a new issue, I'll explain :) [16:53] AlexDaniel:oops, too quick [16:53] Sorry [16:57] I contributed to the first general-purpose IRC bot back in the early 90's when I was 15 or so (eggdrop), so my mind is crammed with entirely too much IRC minutiae :-) [17:00] *** sena_kun joined [17:10] *** domidumont left [17:30] *** titsuki left [17:32] .seen [trey-haris]` [17:32] AlexDaniel, I saw [trey-haris]` 2020-01-28T16:57:02Z in #raku-dev: I contributed to the first general-purpose IRC bot back in the early 90's when I was 15 or so (eggdrop), so my mind is crammed with entirely too much IRC minutiae :-) [17:32] :) [17:39] AlexDaniel: yep, I get the permmisiveness, but what will the bot do with people who have underscores in their nicks? [17:39] TreyHarris: it will just work [17:40] it can't distinguish between nickname and nick_name though [17:40] TreyHarris: that's correct [17:40] got it. that's probably an okay balance [17:40] especially given that several IRC clients do nick-avoidance by pre/appending underscores [17:41] it uses that sub for lookups, so both nicknamme` and nick_name will turn into “nickname” [17:41] So sticking an extra underscore in already satisfies my other ticket [17:41] the only issue is if you have two people with similar nicknames on the same channel [17:42] e.g. [Coke] is using [] because there's another user Coke [17:42] now if they both join this channel… :D [17:43] and if someone has a diacritic or other non-ASCII letter character--they'll be addressed as Andr rather than as André. And someone whose entire nick is non-ASCII Unicode letters characters will be just rejected entirely [17:44] TreyHarris: no, because of this line :) https://github.com/Raku/whateverable/blob/110ed6a35662030490a1c7a0fa2642983e26efdb/xbin/Tellable.p6#L55 [17:44] the sub *looks* really stupid, but the behavior is actually pretty neat :) [17:46] TreyHarris: also, people are addressed by the nick of their last message [17:47] ah, yeah. if your nick is Ник12 you'll just become 12, though [17:47] (That first letter is not an H) [17:47] “Ник12 is an erroneous nickname” [17:48] ник12 [17:48] Is it on freenode? Then it doesn't matter. [17:48] that unicode nick extensions page says it should be valid if the server allows it [17:49] if it was allowed I'd run that through confusables first :D [17:49] I'd test it but on freenode I will very quickly get my IP banned if I try more than a few [17:51] maybe it's a good idea to pass it through confusables first for things like O0 and l1i [17:51] but I have never seen anybody do that mistake [17:52] .seen TreyHarr1s [17:52] AlexDaniel, I haven't seen TreyHarr1s around, did you mean TreyHarris? [17:52] and even then you get a helpful response :) [17:52] WeeChat actually chooses TreyHarr1s as my first nick avoidance [17:52] For reasons I can't fathom without examining the source [17:52] TreyHarris: Because TreyHarris_ is too long, I think [17:53] that's why erc turns my nickname into AlexDani` [17:53] Ahh [17:53] WeeChat would probably do AlexDan1el then [17:54] wonderful… yeah maybe I should add confusables mapping too [17:54] TreyHarris: btw here's that code working in real life: https://colabti.org/irclogger/irclogger_log/raku?date=2020-01-28#l278 [17:58] Ugh, looked at my logs and I've become TreyHarr1s but also TreyHarr1--off-by-one error that was corrected at some point I'd imagine [17:59] Yeah, I stopped becoming TreyHarr1s in 2016 and have only become TreyHarr1 since then. [18:02] m: say Str.Range [18:02] rakudo-moar d8e859d00: OUTPUT: «No such method 'Range' for invocant of type 'Str'␤ in block at line 1␤␤» [18:02] Should that work analogously to Int.Range and Rat.Range? [18:03] <[Coke]> Nope. [18:03] m: say Str.min [18:03] rakudo-moar d8e859d00: OUTPUT: «Inf␤» [18:03] m: say Str.max [18:03] rakudo-moar d8e859d00: OUTPUT: «-Inf␤» [18:03] … maybe? [18:03] I mean, what are these? :) [18:03] sourceable6: Str.min [18:03] <[Coke]> That is inconsistent, aye. I'd rather see max and min removed than range added. [18:03] AlexDaniel, https://github.com/rakudo/rakudo/blob/d8e859d/src/core.c/Any-iterable-methods.pm6#L1276 [18:04] sourceable6: Str.min() [18:04] AlexDaniel, https://github.com/rakudo/rakudo/blob/d8e859d/src/core.c/Any-iterable-methods.pm6#L1277 [18:04] m: say Any.min [18:04] rakudo-moar d8e859d00: OUTPUT: «Inf␤» [18:05] that's weird, why would that be in Any [18:05] What's Raku for "is $x a single grapheme?" `.chars == 1`? [18:05] That's the only use for it I can imagine. Subset existence check [18:06] TreyHarris: yep, .chars == 1 [18:07] The only use I can see for Int.Range would seem to be analogous to the use for ["\0"..{$highest_known_codepoint}], and that doesn't seem very useful [18:07] er, strike those square brackets [18:08] it's pseudocode anyway [18:08] m: say ("\0"..'z').elems [18:08] rakudo-moar d8e859d00: OUTPUT: «123␤» [18:09] *** patrickb left [18:09] I've had a proposal drafted for changing how string ranges work but I got stuck [18:10] hmm, what's "sparse unicode padding"? i'm running into this term in a few places but I can't find a definition [18:11] the final issue was having a convenient way for simple things like ‘a’..‘z’ [18:14] m: say so (3 ∈ (0..10)); say so (3 ∈ (0..Inf)); [18:14] rakudo-moar d8e859d00: OUTPUT: «True␤False␤» [18:14] hm? [18:15] m: say so (3 ∈ Int.Range); [18:15] rakudo-moar d8e859d00: OUTPUT: «False␤» [18:15] guess these ranges aren't even useful for the purpose I thought they were useful for [18:16] m: say so (3 ∈ (0..10)); say so (3 ∈ (0..*)); [18:16] rakudo-moar d8e859d00: OUTPUT: «True␤False␤» [18:16] m: say so (3 ∈ (0..10)); say so (3 ∈ (*..*)); [18:16] rakudo-moar d8e859d00: OUTPUT: «True␤False␤» [18:17] The -Inf..Inf (which is what Num.Range returns) would have to be special-cased, but 0..Inf seems like it should just work like any lazy range [18:18] m: say (0..Inf)[12] [18:18] rakudo-moar d8e859d00: OUTPUT: «12␤» [18:19] ¦ rakudo: a08f043953 | (Christian Bartolomäus)++ | src/core.c/VM.pm6 [18:19] ¦ rakudo: [JVM] Unbreak the build [18:19] ¦ rakudo: [18:19] ¦ rakudo: The superfluous closing paren was accidentially added [18:19] ¦ rakudo: with aafa8ca228. [18:19] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/a08f043953 [18:20] Range (elem)/∈ isn't documented [18:25] opened an issue about it https://github.com/Raku/doc/issues/3189 [18:26] *** Kaiepi joined [18:41] Can anyone think of a core routine name that's used for two entirely different things depending on type? (semantically entirely different, not just multis) like, the old example Dog.bark() and Tree.bark() [18:42] there are operators I bet [18:44] *** sena_kun left [18:44] ah, `e` [18:59] *** sena_kun joined [19:01] TreyHarris: if they exist in core, we probably need to fix that [19:01] 2020-01-28T16:03:39Z #raku-dev lizmat https://gitlab.com/tyil/rakudo-star/-/jobs/417548439#L1370 not sure how bad this is [19:02] .tell tyil feels like a wrong version of roast ? [19:02] lizmat, I'll pass your message to tyil [19:02] lizmat: I don't think so... `e` and `from` being two cases that seem obviously acceptable [19:03] methods ? subs? [19:05] bartolin++ # catching JVM issue with a08f04395345ff9f51b93f [19:05] (2020-01-28) https://github.com/rakudo/rakudo/commit/a08f043953 [JVM] Unbreak the build [19:07] lizmat: https://docs.raku.org/routine/from or https://docs.raku.org/routine/e [19:08] I'm not sure the term "e" is a confusable with the .e method [19:09] and I always have thought List.from is a terrible, terrible hack [19:09] That's why I said we don't need to fix it [19:10] from 2014: 1eb7fada84 [19:10] hmmm... why doesn't linkable6 pick this up? [19:10] linkable6: 1eb7fada84 [19:11] 1eb7fada843b75468e15d7e29b90008d68327ea4 [19:11] commit 1eb7fada843b75468e15d7e29b90008d68327ea4 [19:11] guess I don't understand linkable6 [19:12] https://github.com/rakudo/rakudo/commit/1eb7fada84 [19:16] hm, when i add tests for unix socket support to S32-io/IO-Socket-INET.t, moarvm throws EMFILE when trying to create the sockets [19:16] which doesn't make a whole lot of sense [19:16] maybe the threading in it's buggy [19:21] 1eb7fada843b7 [19:21] hmmmmm [19:21] lizmat: that's a good question! [19:21] I don't know! [19:22] foo d8e859d00 [19:22] (2020-01-28) https://github.com/rakudo/rakudo/commit/d8e859d000 Make has Str $.a = 42 a compile time failure [19:23] lizmat: did you happen to see my questions/comments last night ? [19:23] lizmat: can you file a bug report please? [19:23] AlexDaniel: will do [19:23] MasterDuke: please remind me :-) [19:24] it's a new feature that we didn't have before, but honestly I have absolutely no idea why it doesn't find that [19:24] it should work [19:25] lizmat: https://colabti.org/irclogger/irclogger_log/raku-dev?date=2020-01-27#l386 and then some discussion with AlexDaniel following [19:26] oooh I think I know why… [19:28] lizmat: it, uh… found this result too: https://github.com/tony-o/deb-rakudodaily/commit/1eb7fada843b75468e15d7e29b90008d68327ea4 [19:28] ah, i just need to do the UNIX socket tests before the IP ones [19:28] and refused to print anything because it doesn't know which one you wanted [19:29] tony-o_: what is that repo, btw? [19:30] lizmat: that's easily fixable, I just need to figure out the best way to pick the right result [19:30] amount of github stars maybe? [19:31] * AlexDaniel sleep & [19:31] rakudo/rakudo first ? [19:34] ¦ roast: 7ae5e2be11 | (Ben Davies)++ | S32-io/IO-Socket-INET.t [19:34] ¦ roast: Add tests for IO::Socket::INET UNIX socket support [19:34] ¦ roast: review: https://github.com/perl6/roast/commit/7ae5e2be11 [19:35] *** MasterDuke left [19:35] lizmat: idk what that implies, except that something needs fixing [19:35] 2020-01-28T19:02:24Z #raku-dev tyil feels like a wrong version of roast ? [19:40] ¦ problem-solving: treyharris assigned to JJ Issue Routine doc pages need front matter https://github.com/Raku/problem-solving/issues/155 [19:43] ↑ I wrote the above issue to consider the issues I've brought up before about needing a place for overall routine documentation aside from type-specific docs [19:57] ¦ rakudo: 05b5f81b67 | (Elizabeth Mattijsen)++ | src/Perl6/Metamodel/BUILDPLAN.nqp [19:57] ¦ rakudo: Move typecheck thrower to separate method [19:57] ¦ rakudo: [19:57] ¦ rakudo: so we can use it from multiple places [19:57] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/05b5f81b67 [19:59] *** squashable6 left [20:00] *** squashable6 joined [20:02] heh, when I got a reply to my answer to T&M, "That was one of the most illuminating things I have ever read. Thank you for taking the time to write that.", I actually thought it came from T&M initially and was gobsmacked. But, no, the earth is still in its orbit :-) [20:03] yeah :-) [20:21] TreyHarris++ # perseverance [20:30] *** MasterDuke joined [20:40] sena_kun: yeah, i'm also seeing a little slower parse times for rakudo recently [20:44] *** sena_kun left [20:53] The most-recent commit is no longer shown at the bottom of docs.raku.org or docs.p6c.org... is it hiding somewhere? I'm just trying to figure out what version I'm seeing in the index [20:56] <[Coke]> I believe that was disabled because of churn. [20:56] <[Coke]> You could probably follow the build log. [20:56] <[Coke]> jj would probably know for sure [21:00] bisectable6: subset A of Int; class B { has A:D $.a is default('') = 42 } [21:00] lizmat, Bisecting by exit code (old=2015.12 new=05b5f81). Old exit code: 0 [21:00] lizmat, bisect log: https://gist.github.com/8eaabcbc417346f7efffe15a9bdc6104 [21:00] lizmat, (2017-07-31) https://github.com/rakudo/rakudo/commit/148ba7f2e4de8f33e8436267a4b0c9042a171d82 [21:00] *** sena_kun joined [21:03] [Coke]: "churn" meaning pages that didn't change changed since the commit was always changing? Could that be rectified by using the commit of the last change that changed a page's content, so if commit a1b2cd3 changed Foo::bar, only /type/Foo and /routine/bar would change? [21:03] (Notionally "could"; I'm aware it's not easy coding.) [21:04] bisectable6: subset A of Str where /^ foo/; class B { has A $.a = "foobar" } [21:04] lizmat, Bisecting by exit code (old=2015.12 new=05b5f81). Old exit code: 0 [21:05] lizmat, bisect log: https://gist.github.com/dc0176feeac57de322458c33b852e40b [21:05] lizmat, (2020-01-28) https://github.com/rakudo/rakudo/commit/d8e859d000fa658766266a45f99e58661dec7b0e [21:05] vrurg: that is what's killing URI atm [21:06] <[Coke]> TreyHarris: yes, I imagine that scheme would be acceptable. [21:06] ++TreyHarris [21:07] doesn't tellable6 have a trick to get it to reference the current moment in archives so you don't have to repeat info in-channel? [21:07] I thought I remembered such a thing [21:11] .tell jmerelo please see https://colabti.org/irclogger/irclogger_log/raku-dev?date=2020-01-28#l580 in re commit sha's and doc churn [21:11] TreyHarris, I'll pass your message to jmerelo [21:17] [Coke]: do you happen to know where is the doc build log? I've been grepping around the repo hoping I'd stumble across a link to it, but no dice [22:24] ¦ rakudo: d18c69b2bc | (Elizabeth Mattijsen)++ | src/Perl6/bootstrap.c/BOOTSTRAP.nqp [22:24] ¦ rakudo: Simplify exception throwing in the bootstrap [22:24] ¦ rakudo: [22:24] ¦ rakudo: - use binding result of if to simplify code [22:24] ¦ rakudo: - don't use existskey, but atkey directly with binding [22:24] ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/d18c69b2bc [22:45] *** squashable6 left [22:45] *** sena_kun left [22:47] *** squashable6 joined [22:59] *** MasterDuke left [23:00] *** sena_kun joined [23:40] Oops, I just remembered you don't give contrafactual analogies to T&M. Expect a request for a way to know the colors of the bits in a native value to be incoming... :-/