00:02 pamplemousse left 00:25 titsuki joined 00:30 Kaiepi left, Kaiepi joined
Geth nqp: ed8d95082a | (Vadim Belman)++ | tools/templates/Makefile-backend-common.in
Make stage 2 always fully rebuild upon changes in sources

As has been discussed here: colabti.org/irclogger/irclogger_lo...05-04#l312 stage 2 also tests the ability of stage 1 NQP to compile itself. Thus full rebuild of it is required.
nqp: 70c1ac1e61 | (Vadim Belman)++ | tools/templates/Makefile-backend-common.in
Fix JVM backend build

JVM runtime was skipped without STAGE0_DIR dependency.
nqp: a0e2995f51 | (Vadim Belman)++ (committed using GitHub Web editor) | tools/templates/Makefile-backend-common.in
Merge pull request #625 from vrurg/stage2-full-rebuild

Make stage 2 always fully rebuild upon changes in sources
01:03 titsuki left 01:19 pamplemousse joined
timotimo linkable6: 4cec44a3 01:26
linkable6 (2020-02-23) github.com/rakudo/rakudo/commit/4cec44a30f Implement index(string, @needles)
timotimo linkable6: aaaaaa 01:28
linkable6: 00000
linkable6: 0000
linkable6: 000 01:29
02:59 pamplemousse left
AlexDaniel timotimo: there are hundreds of commits like this, it simply refuses to link them x) 06:16
06:24 anatofuz joined 06:25 anatofuz_ joined 06:26 anatofuz left 06:27 anatofuz_ left 06:28 anatofuz joined
Geth rakudo: c0b5fb282c | (Elizabeth Mattijsen)++ | src/core.c/Instant.pm6
Make Instant.perl a bit less noisy

By removing the "Bool::False" when it is not needed, and use normal stringification for the Rat representing the posix value.
rakudo: c2dc0e57ce | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | 397 files
Merge branch 'master' into instant-perl
rakudo: 8989eb9118 | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | src/core.c/Instant.pm6
Merge pull request #3279 from rakudo/instant-perl

Make Instant.perl a bit less noisy
nine tbrowder: can you show me what you've got so far? 06:44
07:02 samcv left 07:03 samcv joined 07:05 MasterDuke joined 07:09 jjatria left, sivoais left, masak left, moritz left 07:13 Geth left, Geth joined 07:15 jjatria joined, sivoais joined, masak joined, moritz joined 07:21 sivoais left 07:22 sivoais joined 07:48 sena_kun joined
AlexDaniel c: WHY-on-role-group say 42 07:57
committable6 AlexDaniel, ¦WHY-on-role-group: «42␤»
AlexDaniel jnthn: there's your pull request :) github.com/rakudo/rakudo/pull/3549
08:07 Kaiepi left 08:08 Kaiepi joined
Geth rakudo/master: 9 commits pushed by (Suman Khanal)++, (Aleks-Daniel Jakimenko-Aleksejev)++ 08:23
08:51 jjmerelo joined 08:52 sena_kun left, sena_kun joined
sena_kun 08:53
tellable6 2020-05-05T07:14:34Z #moarvm <nine> sena_kun: you do know about MoarVM/tools/release?
sena_kun nine, no idea, I used `make release VERSION=2020.05` which is used in the release guide. 08:54
And release make target is just `./tools/release.sh $(VERSION)` so I guess. 08:55
08:57 jjmerelo left
jnthn AlexDaniel: Yeah, not sure what to do with that. I guess maybe the best way is to version it and update the tests... I'm fine if somebody else picks it up and does that bit, given I'm on with quite a few other things :) 09:02
09:07 Altai-man_ joined 09:09 sena_kun left
AlexDaniel lizmat: t/spec/S02-types/instants-and-durations.t ? 09:33
09:34 jjmerelo joined
AlexDaniel lizmat: in 6.d-errata branch too 09:34
jjmerelo Hi again
AlexDaniel o/
Altai-man_ releasable6, status
releasable6 Altai-man_, Release date for Rakudo 2020.05 is listed in “Planned future releases”, but it was already released.
Altai-man_, and I oop! Backtrace: gist.github.com/d3fdc4b65feee7ad8e...923d3302dc 09:35
jjmerelo The application for season of docs has been submitted
Altai-man_ nooooo
jjmerelo Altai-man_ ++, great job with this new release.
Altai-man_ >2020-05-30 Rakudo #136 (Altai-man + Releasable) 09:36
>Release date for Rakudo 2020.05 is listed in “Planned future releases”, but it was already released.
I am kinda confused
lizmat Files=1305, Tests=111245, 213 wallclock secs (28.73 usr 8.42 sys + 2992.34 cusr 278.88 csys = 3308.37 CPU)
^^ before release
Altai-man_ pls don't be bad 09:37
AlexDaniel Altai-man_: “The next release of Rakudo (#136), is tentatively scheduled for 2020-05-30.” 09:41
Altai-man_ Yup, and?
AlexDaniel how can we have two 2015.05 releases? 09:42
sorry 2020.05 releases*
Altai-man_ d'oh
So next release would be in almost two months again? 09:43
AlexDaniel Altai-man_: I think the date is just wrong, that's it
the announcement was also a bit too optimistic but don't worry about it
Altai-man_ I mean, we release now to avoid waiting for 3-4 damn weeks more, but that means we have to either move all the next release dates to start of the month or wait another two of them. 09:44
AlexDaniel third Saturday of June is 20th 09:45
so 1.5 months away
sounds totally OK? 09:46
Altai-man_ *shrugs*
MasterDuke might get some of the new dispatcher work in then 09:47
Altai-man_ That's the plan, I think.
Geth rakudo: 4f672c2756 | (Ben Davies)++ (committed by Aleks-Daniel Jakimenko-Aleksejev) | lib/NativeCall/Compiler/GNU.rakumod
Improve GNU C++ name mangling

This makes it so the symbol is not assumed to be a constructor when it includes new unless it's the last part of the symbol and infers whether or not the symbol is a constructor by checking if the last two parts of it are identical.
This also mangles Str, Pointer, and CArray attributes with the rw or cpp-const traits properly.
Closes #2884.
linkable6 RAKUDO#2884 [closed]: github.com/rakudo/rakudo/pull/2884 Improve GNU C++ name mangling
Geth ¦ problem-solving: AlexDaniel assigned to jnthn Issue A way to control Rat's behavior when it is running out of range for its denominator github.com/Raku/problem-solving/issues/185 09:55
AlexDaniel 2 more PRs to get down to 3 pages 09:56
lizmat bisectable6: old=2020.01 my $i := Instant.from-posix(33/7, False); is-deeply $i, $i.raku.EVAL 10:15
bisectable6 lizmat, On both starting points (old=2020.01 new=4f672c2) the exit code is 1 and the output is identical as well
lizmat, Output on both points: «04===SORRY!04=== Error while compiling /tmp/WQn5i46JjO␤Undeclared routine:␤ is-deeply used at line 1␤␤»
lizmat bisectable6: old=2020.01 use Test; my $i := Instant.from-posix(33/7, False); is-deeply $i, $i.raku.EVAL
bisectable6 lizmat, Bisecting by exit code (old=2020.01 new=4f672c2). Old exit code: 0
lizmat, bisect log: gist.github.com/03324aa7eccad626e5...6bd85aa975
lizmat, (2019-11-05) github.com/rakudo/rakudo/commit/c0...c20aae971d
lizmat How can a commit from before 2020.01 be the cause when bisecting from 2020.01 ? 10:17
AlexDaniel ^^ ??
ah, it got merged ?
AlexDaniel lizmat: it's just a date, yeah
# expected: Instant.from-posix(4.714286) 10:18
# got: Instant.from-posix(4.714286)
AlexDaniel squints
I… don't see any difference??
m: my $i := Instant.from-posix(33/7, False); dd $i; dd $i.raku.EVAL 10:20
camelia Instant.from-posix(4.714286)
lizmat yeah... its 33/7, which doesn't represent as a float, so some kind of rounding issue
10:29 dogbert17 joined, timotimo left, ccamel left, dogbert11 left, camelCaser joined 10:30 timotimo joined
tbrowder nine: yes, i'll put it up on my fork this morning. i'm struggling with the actual tests. i'm trying to "testify" the two short scripts into a working two tests which die-ok and live-ok but no luck so far. 10:40
Geth rakudo: f506cc039d | (Elizabeth Mattijsen)++ | src/core.c/Instant.pm6
Fix Instant.raku for Rational values

Instant.raku was internally depending on Instant.Str, which uses .gist, which creates issues for values such as 33/7
nqp/new-disp: 65eaa1bbcd | (Jonathan Worthington)++ | 2 files
Mark literal call arguments in callsites
rakudo: ee005d8ba4 | (Ben Davies)++ | 2 files
Improve X::Syntax::Variable::MissingInitializer's message

This makes the messages it can give more consistent. On top of that, attributes now get referred to as attributes instead of variables and the "is required" trait now gets mentioned with them.
rakudo: a601e7f38b | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 2 files
Merge pull request #3589 from Kaiepi/attribute-missing-initializer

Improve X::Syntax::Variable::MissingInitializer's message
roast: c2ae95f082 | (Ben Davies)++ | S02-types/subset-6e.t
Update tests WRT X::Syntax::Variable::MissingInitializer's new msgs
roast: 66c48fb802 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | S02-types/subset-6e.t
Merge pull request #632 from Kaiepi/attribute-missing-initializer

Update tests WRT X::Syntax::Variable::MissingInitializer's new msgs
10:52 squashable6 left 10:53 squashable6 joined 11:07 sena_kun joined 11:09 Altai-man_ left
Geth rakudo: 37646b869b | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/PrecompilationStore/File.pm6
Add CACHEDIR.TAG to mark cache dirs as cache

As suggested in github.com/rakudo/rakudo/pull/1796 , but that PR bitrotted, so this commit implements the idea.
lizmat argh... was too focussed on it not breaking installation of modules, that I forgot to run spectests :-( 11:37
Geth rakudo: c3bdb617cb | (Elizabeth Mattijsen)++ | t/02-rakudo/reproducible-builds.t
Make sure we remove the CACHEDIR.TAG file as well
lizmat nine: I'me seeing t/spec/S01-perl-5-integration/method.t pass test #2 after this 11:44
"blessed # TODO P5 classes not yet shadowed in P6" 11:45
nine sena_kun: tools/release automates the first 6 steps of the release guide (sans the actual cleaning up of commits in the ChangeLog). I guess we should adapt the release guide to replace those steps with a call to the script 11:47
Most of all it makes the tests with NFG_DEBUG painless
sena_kun nine, is there anything I've done wrong or?
nine lizmat: it's Inline::Perl5 0.48 which implemented the tested functionality 11:49
sena_kun: nah, you could have just saved some time
lizmat Ah, I guess I just reinstalled an updated Inline::Perl5 then 11:50
after I nuked my install to test the CACHEDIR.TAG functionality 11:51
Geth roast: 6587491dfd | (Elizabeth Mattijsen)++ | S32-exceptions/misc.t
Update faulty test count
tbrowder .tell nine PR pushed just now 11:54
tellable6 tbrowder, I'll pass your message to nine
lizmat a strange performance difference: 12:01
m: my @a = ^1000; for ^1000 { my @b = @a.map: * + 1 }; say now - INIT now
camelia 0.346152
lizmat m: my @a = ^1000; for ^1000 { my @b = @a.rotate(3) }; say now - INIT now
camelia 0.8259712
lizmat the slowdown appears to come from github.com/rakudo/rakudo/blob/mast...ay.pm6#L31 12:02
not getting speshed, inlined or JITted
and taking 50%+ of CPU in that benchmark 12:03
feels like LHF for someone :-) 12:04
AlexDaniel c: 2020.05 say 42 12:05
committable6 AlexDaniel, ¦2020.05: «Cannot test this commit (Commit exists, but an executable could not be built for it)»
AlexDaniel hmm
perhaps just bad luck
lizmat perhaps it should automatically try for the next commit that *did* build ?
jnthn Hm, when building Rakudo I'm seeing a flood of stuff like: 12:06
Use of uninitialized value $str in substitution (s///) at /home/jnthn/dev/rakudo/3rdparty/nqp-configure/lib/NQP/Config.pm line 1402.
[Tux] Moving into the right direction …
Rakudo version 2020.05-41-gc3bdb617c - MoarVM version 2020.05-2-g60b567089
csv-ip5xs0.821 - 0.835
csv-ip5xs-208.322 - 8.412
csv-parser24.811 - 26.056
csv-test-xs-200.378 - 0.386
test7.608 - 7.614
test-t1.965 - 1.985
test-t --race0.882 - 0.964
test-t-2031.317 - 33.059
test-t-20 --race9.573 - 9.801
jnthn Hm, and the installed result is broken...wonder if that's local changes or not 12:07
lizmat jnthn: I'm not seeing that and I just rebuild completely from scratch after nuking my install dir
sena_kun ayaya, test-t looks healthy, that's a good sign
AlexDaniel damn I should've checked the output first before removing the build
lizmat: first of all it shouldn't fail to build something that's buildable… 12:08
jnthn ohh...I was sat on the rakuast branch and didn't notice :)
lizmat AlexDaniel: que?
AlexDaniel lizmat: it was re “perhaps it should automatically try for the next commit that *did* build” 12:09
lizmat ah, ok
AlexDaniel c: 2020.05 say 42 12:10
committable6 AlexDaniel, ¦2020.05: «42␤»
AlexDaniel c: 2020.05^,2020.05^^,2020.05^^^,2020.05^^^^,2020.05^^^^^ say 42 12:11
committable6 AlexDaniel, ¦2020.05^: «Cannot test this commit (Commit exists, but an executable could not be built for it)» ¦2020.05^^,2020.05^^^,2020.05^^^^,2020.05^^^^^: «42␤»
AlexDaniel shareable6: 2020.05^
shareable6 AlexDaniel, whateverable.6lang.org/2020.05^
AlexDaniel error: pathspec '2020.05' did not match any file(s) known to git 12:12
sena_kun looks at 2020.05 tag 12:13
AlexDaniel something about tags being pushed at different times, I think 12:14
it's OK now, it just failed to build for these two commits
12:17 anatofuz left
lizmat R3664 # so it doesn't fall through the cracks 12:19
R#3664 # so it doesn't fall through the cracks
linkable6 R#3664 [open]: github.com/rakudo/rakudo/issues/3664 ArrayReificationTarget.push not speshing
jjmerelo The application for Google's summer of docs is in, but we can still add ideas to the repository perl-foundation-outreach.github.io...ocs-ideas/ Anything that's Raku-related is game. Just create a PR 12:31
There're again only 50 slots, so it's going to be difficult to get in. Main thing working in our favor is that our application got rejected last year. Still, 50 slots are too few... 12:32
So, anyway, a diversity and quantity of documentation projects will also help us, so please feel free to add 12:33
lizmat afk for a few hours& 12:34
jjmerelo I'll be in a few minutes... 12:38
jjmerelo goes afk for lunch and siesta 12:43
MasterDuke huh, a profile of the code in R#3664 shows that push not being speshed or jitted, but a spesh log disagrees 12:45
linkable6 R#3664 [open]: github.com/rakudo/rakudo/issues/3664 [performance] ArrayReificationTarget.push not speshing
MasterDuke no lego jit bails, and there is an 'after' spesh 12:46
a perf report does look a little odd though. 2nd most expensive is MVM_spesh_arg_guard_run at 5.2% and next is resolve_using_guards also at 5.2% 12:47
12:47 jjmerelo left
nine tbrowder: that's still 5 times as many LOC as the whole of Inline::Perl5 :/ 12:48
tellable6 2020-05-05T11:54:08Z #raku-dev <tbrowder> nine PR pushed just now
tbrowder yep, it will take some time to trim more 12:49
and a lot more effort. 12:51
if you have the fix on a branch i can test my prog with it before maybe wasting time on trimming 12:52
we could also keep it zipped until build/test time 12:53
i mean just store the zipped file in github 12:55
i'm willing to work on the trimming but i can't guarantee any size target 12:56
or time table 12:57
nine Looks like all that was needed was github.com/niner/Inline-Perl5/comm...5e6a38d39c
tbrowder cool! maybe i can create a simpler test without all tha Excel overhead 13:00
in the meantime i can press on with my pressing project--thanks! 13:01
13:07 Altai-man_ joined 13:09 pamplemousse joined, sena_kun left
Geth nqp: 45aedacdfd | (Timo Paulssen)++ (committed by timo) | 18 files
Don't bind an int attribute to 0 directly after construction

since we construct objects null-initialized anyway.
timotimo i thought after the release this is probably just fine to merge 13:14
tbrowder nine: will you require a test to release the fix? 13:29
Geth rakudo: 48e073e2db | (Ben Davies)++ | 3 files
Allow debuggers to be specified by environment variables

This makes it so gdb/lldb/valgrind are used by default, but may be overridden by RAKUDO_GDB/RAKUDO_LLDB/RAKUDO_VALGRIND environment variables.
rakudo: b01b0120bc | (Ben Davies)++ | tools/templates/moar/rakudo-gdb-m.in
Default to using egdb when possible in rakudo-gdb-m
rakudo: 6a79e18fbc | (Vadim Belman)++ (committed using GitHub Web editor) | 3 files
Merge pull request #3489 from Kaiepi/debugger-overrides

Allow debuggers to be specified by environment variables
¦ problem-solving: Skarsnik assigned to AlexDaniel Issue Nativecall, native trait library usage rework github.com/Raku/problem-solving/issues/186 13:39
13:45 squashable6 left, squashable6 joined
Geth ¦ problem-solving: AlexDaniel assigned to jnthn Issue Nativecall, native trait library usage rework github.com/Raku/problem-solving/issues/186 14:18
¦ problem-solving: AlexDaniel self-unassigned Nativecall, native trait library usage rework github.com/Raku/problem-solving/issues/186
14:48 jjmerelo joined 15:07 sena_kun joined 15:09 Altai-man_ left
Geth ¦ problem-solving: JJ assigned to jnthn Issue Use a grammar for command line options github.com/Raku/problem-solving/issues/187 15:45
jjmerelo OK, I need a bit of help with testing rakudo stuff 16:09
I'm trying to carry over this PR github.com/rakudo/rakudo/pull/368/files
It adds a couple of named arguments to ok, so it's not critical, I guess, so good choice to cut my teeth there. 16:10
Also, not core, so adding a feature not such a big deal. Right now also the oldest open PR 16:11
OK, what I've done is to test in on S24/1-basic.t, which *already* had tests for it, and they pass; they didn't 16:19
... before. So I'll do it as a PR anyway, just to be on the safe side. OK?
AlexDaniel jjmerelo: don't merge it 16:20
jjmerelo I wasn't thinking about doing it. I'm creating a new PR for it. 16:22
Geth rakudo: JJ++ created pull request #3665:
Incorporates @paultcochrane patch for ok with named args.
AlexDaniel jjmerelo: and don't merge your own PR also 16:23
jjmerelo OK.
Anyway, my point is that would be the way to proceed. Change, test with roast, PR if you're not sure, right? 16:25
AlexDaniel it adds a named argument that nobody really needs
and it does so for just `ok`
jjmerelo `is` needs it too..
AlexDaniel I don't even see any justification, it looks like there are some speculated tests or something?
jjmerelo Correct
AlexDaniel we shouldn't add features just because, first discuss it in problem-solving if there's a problem at all 16:26
jjmerelo But in this case, tests are already in roast
so it's spec
AlexDaniel if they're TODO-ed then I don't consider it spec
a lot of these old tests are no longer relevant 16:27
jjmerelo It's these tests github.com/Raku/roast/blob/master/....t#L27-L31
AlexDaniel no, just the last two 16:28
ah… wait so these already pass?
simply because :todo is ignored?
jjmerelo No, 2 to 5 don't pass 16:29
any of them with desc or todo
Unexpected named argument 'desc' passed
... They do now...
AlexDaniel ? O_o 16:30
do we skip this whole file or something?
jjmerelo Beats me 16:31
AlexDaniel yeah, it's not in spectest.data
jjmerelo It does not have any fudge mark...
So tests are not tested?
AlexDaniel jjmerelo: yeah, some files are not used at all
jjmerelo :O
So 16:32
AlexDaniel anyway, close both PRs, open a problem-solving ticket discussing whether we need :todo named arg at all
and we'll reject it from there… :D
jjmerelo OK, but does not _really_ solve the side problem
why is 1-basic.t excluded? 16:33
Anyway, doing that.
AlexDaniel I guess it's easier than fudging all tests in it?
[Coke] if a file is not in any variant of spectest.data, there is definitely an argument to remove the file
jjmerelo AlexDaniel some tests definitely pass... 16:34
AlexDaniel jjmerelo: yeah, some basic ones pass, that's fine
does anybody know the justification for :todo? Where does it come from? 16:35
[Coke] AlexDaniel: what do you mean, justification?
AlexDaniel I checked S24 but it doesn't seem to be there
[Coke] of todo tests at all?
prior testing art. 16:36
"Here's a test that we can run. we want to know when it passes as soon as it starts passing."
as opposed to skip: "here's a test we can't even run, so leave it here but don't try to execute it."
AlexDaniel [Coke]: I'm talking about the :todo named arg, see these tests: github.com/Raku/roast/blob/6587491....t#L30-L31
[Coke]: seems like somebody looked at the tests and implemented it: github.com/rakudo/rakudo/pull/368 16:37
and I'm like… why? why do we need a named arg like this?
“We need to test that these functions produce 'not ok' at the right times, 16:38
too. Here, we do that by abusing :todo to mean "supposed to fail." Thus,
no ":todo" failure indicates a missing feature.”
[Coke] It's not implemented just to support that comment.
is your argument that we already have todo(), so we don't need a per-test version? 16:39
AlexDaniel sorry I'm dense, what does that mean?
[Coke] (per-test == named arg for a particular test invocation)
AlexDaniel [Coke]: yeah, I just want to know why we need a per-test version 16:40
do we need :skip also?
[Coke] I don't think so, since a skipped test sometimes can't even be declared, let alone executed. 16:41
Geth ¦ problem-solving: JJ assigned to jnthn Issue Should we have named arguments in test routines? github.com/Raku/problem-solving/issues/188
AlexDaniel right
[Coke] so, :todo to me is a convenience. 16:42
also timtowtdi
with :todo, you don't have to take extra care when re-ordering tests 16:43
jjmerelo [Coke] also, tests are already there. Maybe check out the commit that created them...
[Coke] AlexDaniel can do that if he likes, sure.
jjmerelo Well, not very informative, but... github.com/Raku/roast/commit/472a4...49867ad85f
[Coke] those are adding the tests themselves, not the implementation of :todo. 16:44
(in case anyone else is digging)
AlexDaniel jjmerelo: I edited the ticket dramatically to remove mentions of :desc :) 16:45
jjmerelo: we already have :desc, it's not a question 16:46
oh, so we need to dig it in mu repo 16:47
jjmerelo AlexDaniel not as named argument, but OK
[Coke] So I missed some initial context: we don't have :todo yet, this test is implicitly proposing we add it?
AlexDaniel jjmerelo: oh right, yeah I guess
[Coke]: exactly
[Coke] I wouldn't add it, then. 16:48
AlexDaniel [Coke]: and then somebody submitted a PR adding it, so we're trying to decide what to do with the PR
[Coke] It's a convenience, but I don't think it's required. Do we have anyone who currently "owns" testing? 16:49
jjmerelo OK, timeline is: somebody wanted it and created tests for it 10 years ago (or more). Paul Cochrane created a PR 5 years ago that added it. I reproduced it again, found the tests, they pass, and created another PR...
[Coke] "because we are using this module to test Pugs itself, 16:51
which I think dates the test files and then the PRs based on them. 16:52
jjmerelo feels it's dejá vu all over again when AlexDaniel reopens issues/PRs I've closed...
AlexDaniel x) I marked it as a Draft
[Coke] I also don't think abusing TODO would work with something like prove. an unexpected pass is NOT a failure. 16:53
AlexDaniel github.com/perl6/mu/commit/d6da37b...50551d534e 16:54
d6da37b6f7b7 16:55
linkable6 (2009-06-25) github.com/perl6/mu/commit/d6da37b6f7 [ere-smo] added &is to Test.pm
AlexDaniel 2687c304438cc
linkable6 gist.github.com/b35f39b8cab70754c9...b7d483c254
AlexDaniel (2006-07-09) github.com/perl6/mu/commit/2687c30443 added t/02-test-pm/ which consolidates tests for …
71db8dd7e4 16:56
linkable6 (2005-08-11) github.com/perl6/mu/commit/71db8dd7e4 ...undo...
AlexDaniel 26e52f822b0
linkable6 (2005-08-11) github.com/perl6/mu/commit/26e52f822b Initial Pugs checkin.
AlexDaniel cb75ba229e
linkable6 (2005-04-22) github.com/perl6/mu/commit/cb75ba229e start of the removal of todo_* functions; see ext/Test/ChangeLog for details;
jjmerelo Basically the original ok did have them 16:57
AlexDaniel .tell jnthn perhaps another opportunity to reject a feature that nobody is asking for: github.com/Raku/problem-solving/issues/188 16:59
tellable6 AlexDaniel, I'll pass your message to jnthn
jjmerelo AlexDaniel But some commit from 15 years ago wants that! 17:02
17:07 Altai-man_ joined 17:09 sena_kun left 17:22 softmoth joined 17:23 Xliff joined 17:35 Xliff left
timotimo my rewrite of the hyper codegen optimizer pass now handles this properly: @result = (@input1 Z+ @input2) >>+<< @input2 18:08
with differently-sized input arrays
MasterDuke nice 18:28
19:08 sena_kun joined 19:09 Altai-man_ left 19:20 lucasb joined
Geth nqp: 39b348c6c9 | Coke++ | docs/ops.markdown
add simplistic docs for buffertocu
tbrowder .tell nine that commit fixed issue #147--i owe you a test file. thanks! 19:51
tellable6 tbrowder, I'll pass your message to nine
Geth rakudo/hyper_codegen: 587d514c87 | (Timo Paulssen)++ | src/Perl6/Optimizer.nqp
implement proper size check and zip metaop
20:22 jjmerelo left
Geth nqp: c758eb3999 | Coke++ | docs/ops.markdown
Revert "add simplistic docs for buffertocu"

This reverts commit 39b348c6c9f2e976d86e65be109a25ce69ea920e.
Incorrect docs.
20:59 Kaiepi left, Kaeipi joined, Kaeipi left 21:00 Kaeipi joined
timotimo [JSON::JWT] ===SORRY!=== Error while compiling /home/timo/.zef/store/P6-JSON-JWT.git/18114226e9c4475ce70d23974a8286e562b4c650/t/02-encode.t 21:02
[JSON::JWT] Could not find JSON::JWT in:
[JSON::JWT] file#/home/timo/.zef/store/P6-JSON-JWT.git/18114226e9c4475ce70d23974a8286e562b4c650
the heck is happening
oh, the version i got has a META.info, could that be the problem?
that it's not a META6.json?
sena_kun timotimo, maybe it assumes `-Ilib` or something? Not updated META.info tells something about bitrot. 21:03
timotimo it's got a meta6 in the github repo 21:04
i'm probably getting it from cpan?
sena_kun hmmm
Is it on CPAN?
timotimo Commits on Apr 20, 2018 21:06
Rename META file
it *is* pulling from github what the heck
i'll just nuke zef's store
21:07 Altai-man_ joined
timotimo that fixed it 21:08
21:09 sena_kun left 21:14 Altai-man_ left, softmoth_ joined 21:16 softmoth__ joined 21:17 softmoth left 21:19 softmoth_ left 21:27 softmoth__ left, softmoth__ joined 21:33 softmoth joined 21:35 softmoth__ left 21:36 softmoth_ joined 21:38 softmoth left 21:42 softmoth_ left 22:29 lucasb left
Geth rakudo: ef90599e2b | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/PrecompilationStore/File.pm6
Make sure newly created dir is writeable
23:17 Xliff joined 23:29 squashable6 left 23:30 squashable6 joined, squashable6 left 23:31 squashable6 joined 23:41 softmoth joined