Perl 6 language and compiler development | Logs at colabti.org/irclogger/irclogger_log/perl6-dev | For toolchain/installation stuff see #perl6-toolchain | For MoarVM see #moarvm
Set by Zoffix on 27 July 2018.
AlexDaniel fresh blin, if anyone is interested: gist.github.com/AlexDaniel/6026451...c46ff6a179 00:29
note that there are some new failures 00:30
this: gist.github.com/AlexDaniel/6026451...rview-L649
AlexDaniel and this: gist.github.com/AlexDaniel/6026451...rview-L182 00:30
jnthn: also this… weird gist.github.com/AlexDaniel/6026451...rview-L560 00:31
that's it I think
Geth rakudo: vrurg++ created pull request #2679:
Issue 2613		 02:57
roast: vrurg++ created pull request #511:
Test for #2613		 03:16
MasterDuke vrurg++, glad to see new people getting involved 03:21
vrurg o/
But it's scary experience, must admit... ;) 03:22
MasterDuke yes, but also addicting 03:23
vrurg The first dose is for free, aha... 03:25
Geth rakudo: Kaiepi++ created pull request #2680:
Make various methods and operators take Mu over Any		 03:48
Kaiepi that took way too fucking long to debug 03:49
also welcome vrurg 03:50
vrurg thanks everybody 03:51
Kaiepi at least i got to know a little more about how the grammar, actions, and world interact when i got really badly sidetracked 03:52
vrurg Kaiepi: took me half a day to produce a singe line patch. Went as deep as printing debugs from inside moar... 03:53
And there is trully no better way to know the language. Painful yet effective way. ;)
Kaiepi usually fixes are fairly short anyway 03:59
MasterDuke is right though, i started a little over a year ago and now i'm waiting to hear back from the perl committee before doing a lot of work on networking features 04:04
jnthn AlexDaniel: Hmm, that's an interesting (read: weird) failure mode...can't even guess. 10:19
Geth rakudo: 1f004dce25 | (Vadim Belman)++ | .travis.yml
Adjusted for travis build
 10:20
rakudo: b3eb382617 | (Vadim Belman)++ | 2 files
Fixed #2613
rakudo: 0e4a10d028 | (Jonathan Worthington)++ (committed using GitHub Web editor) | src/Perl6/Metamodel/RoleContainer.nqp
Merge pull request #2679 from vrurg/issue_2613

Issue 2613
synopsebot RAKUDO#2613 [open]: github.com/rakudo/rakudo/issues/2613 A role exported from a package with 'is export' cannot be used in ^does with its short name.
roast: c08a6e7979 | (Vadim Belman)++ | 2 files
Test for #2613
 10:22
roast: 571b2a384c | (Jonathan Worthington)++ (committed using GitHub Web editor) | 2 files
Merge pull request #511 from vrurg/issue_2613

Test for #2613
jnthn Hm, that new test fille will have to go into the spectest.data too...
*file
(Taking care of it; will push after spectest passes) 10:23
Geth rakudo: 5be7555fde | (Jonathan Worthington)++ | t/spectest.data
Run S14-roles/typecheck.t
 10:30
Geth rakudo: lizmat self-assigned Crypt::TweetNacl test suite fails since 762c708fdcef github.com/rakudo/rakudo/issues/2681
ada116ef99 | (Elizabeth Mattijsen)++ | lib/NativeCall/Types.pm6

Fixes R#2681. FWIW, the tests of the module pass ok now. But I'm a bit baffled by the fact that there is no visible "iterator" method in the class, so I'm not 100% this is the solution. It *is* however 'make test' and
  'make spectest' clean, and it makes all of the tests of Crypt::TweetNacl
pass.		 13:00
synopsebot R#2681 [open]: github.com/rakudo/rakudo/issues/2681 [regression][⚠ blocker ⚠] Crypt::TweetNacl test suite fails since 762c708fdcef
AlexDaniel releasable6: status 14:19
releasable6 AlexDaniel, Next release in ≈8 days and ≈4 hours. 7 blockers. 163 out of 289 commits logged
AlexDaniel, Details: gist.github.com/19b6ead4334c8b3692...8817fec025
AlexDaniel X_X
travis-ci Rakudo build failed. Elizabeth Mattijsen 'Make NativeCall::Types::CArray an Iterable 14:43
travis-ci.org/rakudo/rakudo/builds/490548408 github.com/rakudo/rakudo/compare/5...a116ef99a2
lizmat restarts the one failing Travis build 14:51
lizmat build came out ok on 2nd try, so assume it was some temporary problem 15:13
Geth rakudo: 0d2658b806 | (Elizabeth Mattijsen)++ | lib/NativeCall.pm6
Fix one forgotten occurrence of .pos

Related to ccf350e , found in
   github.com/perl6/ecosystem-unbitrot/issues/468
Problem spotted by MasterDuke++		 15:55
Geth rakudo: f3f7c5cb63 | (Elizabeth Mattijsen)++ | src/core/Range.pm6
Partially rollback 46409c070e

So that we're back at the status quo of R#2676		 17:22
rakudo: d904b7048b | (Elizabeth Mattijsen)++ | src/core/hash_slice.pm6
Make Mu<> work as before

The original proto of postcircumfix:<{ }> was just |, so it also accepted Mu. This adds Mu to the current signature, and fast-paths the <> case.
synopsebot R#2676 [open]: github.com/rakudo/rakudo/issues/2676 Do we need an overhaul of .ACCEPTS methods wrt Any / Mu?
jdv79 just randomly... my regex heavy canary is unchanged on current. 20:25
:(
essentially the same since a december checkout so at least didn't get worse:) 20:27
timotimo including the bump for today's moarvm merge?
jdv79 i just built a few mintues ago 20:28
my test is on the fly regex heavy so its compiler bound... 20:29
timotimo yeah, that would have the bump for sure
and yeah, that will likely help more with perl6 code than nqp code, so perhaps not improving the compiler parts much
jdv79 i was hopeful but i get why there's no diff
Geth tap-harness6: e1e1d221ed | (Leon Timmermans)++ | lib/TAP.pm
Don't keep reopening devnull
 21:40
japhb Post-merge rakudo build fails to install IO::Socket::Async::SSL:ver<0.7.3> because of test failure "CArray of CArray passed non-CArray object in method ASSIGN-POS" -- already known? 21:42
Geth roast/tap-errors: ff4805c59f | (Leon Timmermans)++ | 2 files
Don't write to OUT in tests
 21:43
roast/tap-errors: afad93f713 | (Leon Timmermans)++ | S32-io/chdir.t
S32-io/chdir.t: don't plan twice in subtest
roast: Leont++ created pull request #512:
Fix various TAP errors		 21:44
AlexDaniel japhb: no 22:20
if that's something that is caused by that merge then please file a ticket
japhb AlexDaniel: It had been a bit since my last HEAD build, so once my currently running (older) build finishes, I'll try with rakudo from right before the bump to check that it is actually ther merge bump that did it. 22:33
japhb It's not the bump, it must have happened before that. 22:57
Oooh, but ada116ef9 may be related. Trying before that one. 22:58
Yup, looks like it was ada116ef9; ada116ef9 doesn't have the IO::Socket::Async::SSL failure (but does of course still have the MoarVM issue that makes Red upset). 23:39
Sorry, *5be7555fd doesn't have that failure

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!