Zoffix travis-ci.org/rakudo/rakudo/builds/157487091 00:54
oh, I updated Perl 6 and modules are missing. 00:55
travis-ci.org/rakudo/rakudo/builds/157487091 00:58
buggable [travis build above] ✓ All failures are due to timeout (1), missing build log (0), or GitHub connectivity (0) 00:59
Zoffix NeuralAnomaly, stats
NeuralAnomaly Zoffix, [✘] Next release will be in 1 week and 5 days. Since last release, there are 35 new still-open tickets (3 unreviewed and 0 blockers) and 5 unreviewed commits. See perl6.fail/release/stats for details
Zoffix buggable, test
huggable, test
huggable Zoffix, Test failed
Zoffix Man, these incidents of RT lying flat on its face coincide with my launching perl6.fail that uses its API every 10 minutes to perform a search. I'm probably just paranoid... can't be the first person to use its API, right? 01:01
MasterDuke the website is working for me 01:05
Zoffix Yeah, it seems to go in and out of service. Flickered about 5 times this morning.
dalek p: 6702a8f | MasterDuke17++ | docs/ops.markdown:
Add stmts to the ToC
 01:11
p: 67b6836 | (Zoffix Znet)++ | docs/ops.markdown:
Merge pull request #306 from MasterDuke17/patch-1

Add stmts to the ToC
Zoffix NeuralAnomaly, stats 01:31
NeuralAnomaly Zoffix, [✘] Next release will be in 1 week and 5 days. Since last release, there are 35 new still-open tickets (0 unreviewed and 1 blockers) and 0 unreviewed commits. See perl6.fail/release/stats for details
Zoffix NeuralAnomaly, blockers
NeuralAnomaly Zoffix, There is 1 release blocker. See perl6.fail/release/blockers
Zoffix, perl6.fail/129198 : Still problems with syntactic errors in the REPL
Zoffix \o/
Really? t/02-rakudo/repl.t runs qqx[$repl-input | $*EXECUTABLE] :/ 01:46
heh "## warning: works only with simple input lines which don't need quoting for Windows"
geekosaur somehow that looks like someone's trying to adapt or simulate a haskell quasiquoter >.> 01:52
dalek kudo/nom: 77d9d41 | (Zoffix Znet)++ | / (2 files):
Syntax errors in REPL must clear on further input

Fixes RT#129198		 01:54
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=129198
Zoffix is trying and failing to make :merge on Proc work 03:07
SIGABORTS on me 03:08
MasterDuke RT #128594
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128594
MasterDuke trying to fix it or use it? 03:09
Zoffix It's not spectested... and I always found it iffy that one has to use .out to get merged output out, so I'm thinking of attempting to have both .out and .err available as normal, and add a .merged where I'll attempt to merge the two outputs....
... after I go out to grab some ice cream :)
MasterDuke, well, I was gonna fix up t/02-rakudo/repl.t to not use qqx[] with poorly quoted input and ran into the crash with the :merge, so I was gonna try to fix it. 03:10
I see timotimo commented with "I've unsuccessfully tried to fix this" which makes me think I may be out of my depth here :P
MasterDuke he had some more comments somewhere 03:11
Zoffix I'm gonna try one more thing on the rakudo level and give up if I fail there.
MasterDuke irclog.perlgeek.de/perl6-dev/2016-0...i_12942223 maybe 03:13
Zoffix Right, the last thing I see is "<timotimo> i think i've found a way to make the shared pipe thing work. it's a bit round-about, but it might just be the right thing" 03:55
But IMO, if there's a way to keep .out and .err intact and provide a .merged it would be more useful than just clobbering .out with merged output and having this hackish-API where you use .out to get merged output :/ 03:57
MasterDuke i do like the idea of a .merged. counter-argument is it would kind of fit with the unixism 2>&1 to put them both in .out 03:58
Zoffix wow, that's quite a list of undocumented nqp stuff :/ 04:06
Kinda wish that weren't the case because it's very hard to hack on rakudo when you see nqp ops you've no idea what they do 04:07
MasterDuke yeah, some are definitely used more than others, like nqp::decont, really wish that was documented 04:09
btw, any idea why "throws-like('str' x 9999999999999999999, X::AdHoc, 'repeat count greater than the NQP limit');" doesn't work? 04:11
i'm using a rakudo built with my PR
Zoffix m: 'str' x 9999999999999999999 04:12
camelia rakudo-moar 77d9d4: OUTPUT«WARNINGS for <tmp>:␤Useless use of "x" in expression "'str' x 9999999999999999999" in sink context (line 1)␤»
Zoffix MasterDuke, it should be throws-like { EVAL q{'str' x 9999999999999999999} }, ....
usually you don't need eval, but you'd still need a block 04:13
MasterDuke ahh, didn't get that from the doc
yep, just surrounding it in {} worked, thanks 04:14
Zoffix And BTW, from what I understand nqp::decont just decontenerizes a thing 04:21
MasterDuke it's the 'just' part i couldn't say for sure 04:22
decontainerizes yes, but what does that mean for different types of containers? failure modes? etc. 04:23
Zoffix ¯\_(ツ)_/¯
MasterDuke exactly. you can figure out a lot from looking at other code, but some documentation would be nice also 04:24
Zoffix Well, I give up. I've no idea what I'm doing (re :merged on Proc) :) 04:41
MasterDuke too bad, i would love to have :merge working for our bots 04:42
dalek kudo/nom: f197ebc | (Zoffix Znet)++ | docs/release_guide_automated.md:
Document which pieces are currently not automated
 05:29
kudo/nom: d33d6ef | (Zoffix Znet)++ | docs/release_guide_automated.md:
Document commit review -> changelog interface
 05:34
kudo/nom: 1e2ecd7 | (Zoffix Znet)++ | docs/release_guide_automated.md:
Typo
 05:35
[Tux] This is Rakudo version 2016.08.1-106-g1e2ecd7 built on MoarVM version 2016.08-35-g5108035 06:04
csv-ip5xs 10.261
test 15.213
test-t 7.325
csv-parser 17.265
nine MasterDuke: at that level, there are only scalar containers. If something is already decontainerized, nqp::decont is a noop. 06:31
MasterDuke: though I am surprised to find that decont is not documented :) 06:32
lizmat: I wonder if you see any improvement on spectest time with my module loading speedups. Loading Test didn't take that long before but we do it quite often in the spectests :) 06:43
arnsholt Huh. My old precomp-singleprocess branch now works 07:48
I have approximately negative confidence this is anything other than an accident
This does make it harder to remember what was the cause of the breakage though >.< 07:52
lizmat nine: Files=1135, Tests=52699, 257 wallclock secs (14.84 usr 4.72 sys + 1594.30 cusr 149.68 csys = 1763.54 CPU) 08:33
machine was not really cold, will be able to tell more tomorrow (after having run a spectest in the middle of the night on a cold machine) 08:34
not seeing much difference, fwiw
nine Ok, thanks. There wasn't much to be expected but it would have been cool if it were at least measurable 08:56
lizmat well, test-t has gone down a bit :-) 08:58
nine within margin of error I suppose 09:00
timotimo Zoffix: it should be easy-ish to do. just i little bit of C and using the libuv API 09:26
Zoffix timotimo, alright, then I'll give it a go once I finish this release automation stuff. 10:44
timotimo that'd be cool :) 10:45
Zoffix NativeCall is not implemented on JVM, is it? 11:38
nine I think it is, but it also seems to be broken. 11:40
Zoffix K. All of t/04-nativecall fails with "parse errors" on my box 11:47
was wondering if it was ever meant to work on JVM in the first place
arnsholt It used to work 11:53
The more recent CPP stuff, and some other stuff, is probably not ported
But I did implement it on JVM a while back
What kind of parse errors do you get though? 11:54
Could be that the NativeCall.pm6 sources use NQP ops that haven't been properly stubbed on JVM
Fixing *that* particular problem should be pretty straightforward 11:55
Implementing the desired behaviours is a different question of course =)
Zoffix TAP parse errors; tests seem to explode with 'java.lang.NullPointerException' gist.github.com/zoffixznet/c80c43d...44d59eeb8a 11:57
arnsholt Weird. In that case I'm not sure off the cuff 11:58
You'd have to dig into the source and see
ll-exception might help 11:59
Zoffix has little interest in JVM backend
don't know Java... It's all alien territory
arnsholt In that case, you'll have to wait for some kind soul to fix it =) 12:01
nine Ah, yes. I also got an NPE trying to load Inline::Perl5 on the JVM but seem to have lost my Java debugging mojo. Couldn't get jdb to tell me where that exception was thrown. 12:05
arnsholt jdb is terrible though, at least if you're used to something like gdb 12:10
I've been considering doing some work on NQP and Rakudo on the JVM, actually 12:11
They could do with some love
And might be cool to see if it's possible to replace our current codegen with something based on Truffle/Graal
nine ++arnsholt # please go on 12:12
arnsholt In my copious spare time, of course =)
Although top of my list is making the NQP JAR a fat JAR that can be invoked simply as java -jar nqp.jar @arguments 12:13
Another angle I'm considering is the single-process precomp branch 12:14
nine arnsholt: you have experimented with single-process precomp, haven't you? 12:16
dalek kudo/nom: 6c39b97 | (Zoffix Znet)++ | docs/release_guide_automated.md:
List JVM backend testing as not part of automated release
 12:18
kudo/nom: f49b387 | (Zoffix Znet)++ | docs/release_guide_automated.md:
Include links to source code of release software
arnsholt nine: Yeah, there's a branch. I even merged an up-to-date nom into it today 12:22
A mere 2343 commits =D
Anyways, it didn't work quite like the forking implementation, because of some datastructure (can't remember which) that was kept across invocations of the compiler 12:23
Sadly (sort of), the bug has gone away when I merge in nom 12:24
I should probably look at it in the state it was and then see what the modern status is
IIRC the problem is likely ordering-sensitive on the SHA1 hashes of the CUs 12:25
nine arnsholt: what's the branch called? 12:26
arnsholt precomp-singleprocess 12:27
nine I'd love if we could get that to work reliably. Would make for example custom repo implementations a lot simpler to handle. 12:32
arnsholt Yeah 12:41
Also, forking a subprocess when we have a compiler object available offends my architectural sensibilities =)
IIRC the problem with the branch was that there was some registry of loaded CUs that wasn't cleared in a new compiler, or something along those lines 12:44
So the dependency resolution went awry, somehow
nine Sounds like something I may have some expertise with. 12:45
MasterDuke jnthn: do you have any opinion on github.com/rakudo/rakudo/pull/867? 13:13
Zoffix Weird. 129192 ticket now showing up on R6 :/ 14:26
*not showing up
m: use Test; isnt 0, 0; done-testing 14:45
camelia rakudo-moar f49b38: OUTPUT«not ok 1 - ␤␤# Failed test at <tmp> line 1␤# twice: '0'␤1..1␤# Looks like you failed 1 test of 1␤»
Zoffix
.oO( "twice" ? )
timotimo 0, and then also 0
so twice 0
Zoffix doesn't follow that logic.... 14:46
m: use Test; my $result = 42; my $expected = $result; isnt $result, $expected; done-testing 14:47
camelia rakudo-moar f49b38: OUTPUT«not ok 1 - ␤␤# Failed test at <tmp> line 1␤# twice: '42'␤1..1␤# Looks like you failed 1 test of 1␤»
Zoffix ¯\_(ツ)_/¯
timotimo you want the thing to be different 14:53
but it turns out it's the same
Zoffix right, "same", not "twice" :)
"Got $got but shouldn't have"
timotimo you passed the same thing twice 14:54
Zoffix No, I didn't pass anything. I'm reading the output of TAP
timotimo *shrug*
"you wanted '42' to not be '42', but '42' is '42'." 14:55
ilmari got: 42, expected: anything else 14:56
mst "error: 42 is obviously the correct answer. did you ask the wrong question?"
ilmari is what perl5's Test::More gives 14:57
m: use Test; is 42, 43; done-testing 14:59
camelia rakudo-moar f49b38: OUTPUT«not ok 1 - ␤␤# Failed test at <tmp> line 1␤# expected: '43'␤# got: '42'␤1..1␤# Looks like you failed 1 test of 1␤»
Zoffix m: use Test; isnt Mu, Mu 15:06
camelia rakudo-moar f49b38: OUTPUT«Cannot resolve caller infix:<===>(Mu, Mu); none of these signatures match:␤ ($?)␤ (\a, \b)␤ (Int:D \a, Int:D \b)␤ (int $a, int $b)␤ (Num:D \a, Num:D \b)␤ (Num $ where { ... }, Num $ where { ... })␤ (num $a, num $b --> Boo…»
timotimo hehehe
Zoffix :) 15:07
timotimo m: use Test; isn't (1 | 2), (5 | 4)
camelia rakudo-moar f49b38: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Undeclared routine:␤ isn't used at line 1. Did you mean 'isnt'?␤␤»
timotimo m: use Test; isnt (1 | 2), (5 | 4)
camelia rakudo-moar f49b38: OUTPUT«ok 1 - ␤»
timotimo oh, huh
ilmari m: use Test; isnt (1|2), (2|3); done-testing 15:08
camelia rakudo-moar f49b38: OUTPUT«not ok 1 - ␤␤# Failed test at <tmp> line 1␤# twice: 'any(1, 2)'␤1..1␤# Looks like you failed 1 test of 1␤»
ilmari well, that's not just misleading, it's blatantly false 15:09
Zoffix :/
ilmari s/misleading/confusing/
timotimo indeed it is
Zoffix I'm fixing the message ATM, btw. Just doing tests
huh 15:14
oh nm
m: use Test; isnt Int, Mu 15:24
camelia rakudo-moar f49b38: OUTPUT«Cannot resolve caller infix:<===>(Int, Mu); none of these signatures match:␤ ($?)␤ (\a, \b)␤ (Int:D \a, Int:D \b)␤ (int $a, int $b)␤ (Num:D \a, Num:D \b)␤ (Num $ where { ... }, Num $ where { ... })␤ (num $a, num $b --> Bo…»
Zoffix m: use MONKEY-GUTS; my Int $x; say nqp::istype($x, Mu)
camelia rakudo-moar f49b38: OUTPUT«1␤»
Zoffix s: &infix:<===>
SourceBaby Zoffix, Sauce is at github.com/rakudo/rakudo/blob/f49b...ny.pm#L418
dalek ast: 29a0186 | MasterDuke17++ | S03-operators/repeat.t:
Tests for RT #125628

Tests for 'a' x NaN, Inf, * and variations.		 15:30
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=125628
dalek ast: 3242f09 | MasterDuke17++ | S03-operators/repeat.t:
Merge pull request #152 from MasterDuke17/RT125628

Tests for RT #125628
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=125628
Zoffix m: my Mu $x .= new; 15:45
camelia rakudo-moar f49b38: OUTPUT«Type check failed in binding to mutate; expected Any but got Mu (Mu)␤ in block <unit> at <tmp> line 1␤␤»
Zoffix is getting too deep into the rabbit hole
m: my $x = Mu.new; say $x ~~ Mu:D
camelia rakudo-moar f49b38: OUTPUT«X::Multi::NoMatch exception produced no message␤ in block <unit> at <tmp> line 1␤␤»
Zoffix m: multi foo (Mu:D $a, Mu:D $b) {say "here"}; multi foo (\a, \b) { say "there"}; my $x = Mu.new; foo class {}, $x 15:47
camelia rakudo-moar f49b38: OUTPUT«X::Multi::NoMatch exception produced no message␤ in block <unit> at <tmp> line 1␤␤»
Zoffix Well, I was gonna add Mu candidates to ===, but that breaks autothreading apparently. (or at least that's what the tests tell me) 15:52
m: dd [ (1|2) == 1 ]
camelia rakudo-moar f49b38: OUTPUT«[any(Bool::True, Bool::False)]␤»
Zoffix m: use Test; isa-ok (1|2 === 1), Junction 15:53
camelia rakudo-moar f49b38: OUTPUT«ok 1 - The object is-a 'Junction'␤»
Zoffix Hm. This fails with my patch, saying it got Bool, but dd [ (1|2) == 1 ] gives the same result.
I wonder if it's just a crappy test
s: Junction, 'isa', \(Junction) 15:56
SourceBaby Zoffix, Something's wrong: ␤ERR: Cannot resolve caller sourcery(Junction, Str, Capture); none of these signatures match:␤ ($thing, Str:D $method, Capture $c)␤ ($thing, Str:D $method)␤ (&code)␤ (&code, Capture $c)␤ in block <unit> at -e line 6␤␤
Zoffix s: (1|2), 'isa', \(Junction)
SourceBaby Zoffix, Sauce is at any("github.com/rakudo/rakudo/blob/f49b....pm#L588", "github.com/rakudo/rakudo/blob/f49b....pm#L588")
Zoffix giggles
timotimo :D :D :D 16:00
Zoffix m: use Test; is Mu, Mu 16:07
camelia rakudo-moar f49b38: OUTPUT«Cannot resolve caller infix:<===>(Mu, Mu); none of these signatures match:␤ ($?)␤ (\a, \b)␤ (Int:D \a, Int:D \b)␤ (int $a, int $b)␤ (Num:D \a, Num:D \b)␤ (Num $ where { ... }, Num $ where { ... })␤ (num $a, num $b --> Boo…»
Zoffix k, this is more prevalent. Screw it.
Would $ok or ($dof and dof) or $ok; get optimised to anything if $dof is false? 16:12
m: my $dof = 0; sub dof { say "ran dof"; exit; }; sub test { my $ok = 0; $ok or ($dof and dof) or $ok; }; say test 16:13
camelia rakudo-moar f49b38: OUTPUT«0␤»
Zoffix m: my $dof = 0; sub dof { say "ran dof"; exit; }; sub test { my $ok = 42; $ok or ($dof and dof) or $ok; }; say test
camelia rakudo-moar f49b38: OUTPUT«42␤»
Zoffix m: my $dof = 1; sub dof { say "ran dof"; exit; }; sub test { my $ok = 42; $ok or ($dof and dof) or $ok; }; say test
camelia rakudo-moar f49b38: OUTPUT«42␤»
Zoffix m: my $dof = 1; sub dof { say "ran dof"; exit; }; sub test { my $ok = 0; $ok or ($dof and dof) or $ok; }; say test
camelia rakudo-moar f49b38: OUTPUT«ran dof␤»
timotimo t/spec/S17-promise/start.t ........................................ Failed 30/47 subtests
ummmmmm ...?
Zoffix Basically, I want the return value to be `$ok` unless `$dof` is set, at which point I want dof() to run when `$ok` is false and dof() will exit() 16:14
dalek kudo/nom: cfb1b23 | (Zoffix Znet)++ | lib/Test.pm6:
Improve failure message on Test::isnt

The `twice: $got` is confusing from the point of view of the user running the test suite. Also, it gives bad results when Junctions are used.		 16:26
Zoffix Test.pm6 needs a refactor. 16:49
Right now it's blessed by the Flying Spaghetti Monster for being holy code. 16:50
benchable6, HEAD my $state = class { has int $.foo = 1}; for ^100 { $state.foo = 0; $state.foo = 1; $state.foo = 3; $state.foo = 4; } 16:52
benchable6 Zoffix, starting to benchmark the 1 given commits
dogbert17 Zoffix: are you around?
Zoffix is asquare 16:53
dogbert17 care to take a look at gist.github.com/dogbert17/f348e0f6...2222c2e28c
Zoffix benchable6, HEAD my int $state = 1; for ^100 { $state = 0; $state = 1; $state = 3; $state = 4; }
dogbert17, looks good to me 16:55
dogbert17 thx, I'll commit it
Zoffix m: my $state = class { has int $.foo = 1}; for ^1000 { $state.foo = 0; $state.foo = 1; $state.foo = 3; $state.foo = 4; }; say now - INIT now; 16:57
camelia rakudo-moar cfb1b2: OUTPUT«Cannot look up attributes in a type object␤ in block <unit> at <tmp> line 1␤␤»
Zoffix m: my $state = class { has int $.foo = 1}.new; for ^1000 { $state.foo = 0; $state.foo = 1; $state.foo = 3; $state.foo = 4; }; say now - INIT now;
camelia rakudo-moar cfb1b2: OUTPUT«Cannot modify an immutable Int␤ in block <unit> at <tmp> line 1␤␤»
Zoffix m: my $state = class { has int $.foo is rw = 1}.new; for ^1000 { $state.foo = 0; $state.foo = 1; $state.foo = 3; $state.foo = 4; }; say now - INIT now;
camelia rakudo-moar cfb1b2: OUTPUT«0.00274253␤»
MasterDuke Zoffix++ bot killer extraordinaire
Zoffix m: my $state = class { has int $.foo is rw = 1}.new; for ^100000 { $state.foo = 0; $state.foo = 1; $state.foo = 3; $state.foo = 4; }; say now - INIT now;
camelia rakudo-moar cfb1b2: OUTPUT«0.0762078␤»
Zoffix m: my int $state = 1; for ^100000 { $state = 0; $state = 1; $state = 3; $state = 4; }; say now - INIT now; 16:58
camelia rakudo-moar cfb1b2: OUTPUT«0.03267211␤»
MasterDuke benchable6, HEAD my int $state = 1; for ^100 { $state = 0; $state = 1; $state = 3; $state = 4; }
Zoffix Hm... Gonna give Test.pm6 a rewrite for fun. Then see if performance is anywhere close to reasonable when done. 16:59
MasterDuke bench: HEAD my int $state = 1; for ^100000 { $state = 0; $state = 1; $state = 3; $state = 4; }; 17:02
benchable6 MasterDuke, starting to benchmark the 1 given commits
MasterDuke, ¦«HEAD»:0.1393
Zoffix :)
dalek kudo/nom: 75ba8cc | (Zoffix Znet)++ | / (2 files):
Prevent too-soon exit when PERL6_TEST_DIE_ON_FAIL is used

The die-on-fail currently exits during proclaim() call, which is prior to diagnostic messages describing the failure are printed.
This work moves the exit to the end of test subroutines. There's certainly a DRYer way to implement this, but performance is a concern.
Fixes RT#129192		 17:11
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=129192
travis-ci Rakudo build errored. Zoffix Znet 'Improve failure message on Test::isnt 17:23
travis-ci.org/rakudo/rakudo/builds/157680608 github.com/rakudo/rakudo/compare/f...b1b236288c
buggable [travis build above] ✓ All failures are due to timeout (1), missing build log (0), or GitHub connectivity (0)
dalek rakudo/nom: 490cf72 | LemonBoy++ | src/core/Enumeration.pm: 17:27
rakudo/nom: Make sure to always ACCEPT the enum elements.
rakudo/nom:
rakudo/nom: As shown in RT#129160 if we try to use an enumeration element as a type
rakudo/nom: for an optional parameter like in the following example we end up with a
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=129160
dalek rakudo/nom: type mismatch between Int:D and Foo.
rakudo/nom: To actually understand what goes wrong we simply have to look at the
rakudo/nom: backtrace: the ACCEPT method that the binder calls is the one from the
rakudo/nom: Numeric role (since enums have Int as base type by default) which in
rakudo/nom: turn calls the infix:<==> operator which in turn calls Bridge.
rakudo/nom: This is where things go south as we actually fail to bind a (Option)
ast: 17557ce | (Zoffix Znet)++ | S24-testing/8-die_on_fail.t:
PERL6_TEST_DIE_ON_FAIL must not exit on failed TODO tests
 17:28
TheLemonMan maybe I should write shorter commit messages 17:31
dalek ast: 350d02b | (Zoffix Znet)++ | S24-testing/8-die_on_fail.t:
test failure diagnostics must show up when PERL6_TEST_DIE_ON_FAIL is used

RT #129192
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=129192
Zoffix TheLemonMan, I think a more correct course of action would be to fix the bot :) 17:32
MasterDuke synopsebot6: source 17:33
synopsebot6: help
synopsebot6: url
Zoffix It's dalek that's less than perfect.
MasterDuke doh, right 17:34
dalek: source
dalek: help
dalek: url
huggable: dunno
huggable MasterDuke, ¯\_(ツ)_/¯
nine Nice! use GTK::Simple down from 6.7 to 3.4s 17:40
Zoffix \o/
nine (was ~20s before yesterday) 17:42
mst \o/ 17:47
MasterDuke isn't there some log somewhere that shows when the docs were last rebuilt? 17:52
TheLemonMan any clue about RT#128846 ? it's as simple as adding 'is rw' to andthen and notandthen, but I don't really know what the design docs say about this 17:53
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=128846
Zoffix MasterDuke, yeah, in the footer "Generated on 2016-09-05T17:06:54Z from HomePage.pod6 from perl6/doc on GitHub, commit 71fde8d. "
There's a build log somewhere too
timotimo docs.perl6.org/build-log/
MasterDuke: ^ 17:54
MasterDuke thanks 17:55
AlexDaniel Zoffix: I'm trying to understand this line, can you help me? ｢$ok or ($die_on_fail and die-on-fail) or $ok;｣
Zoffix: I mean, right there it says $ok or $ok, what's the trick?
Zoffix AlexDaniel, the second $ok will be returned when $die_on_fail is false 17:58
return $ok if $ok; die-on-fail if $die_on_fail; return $ok 17:59
AlexDaniel I see
Zoffix Granted, it's probably not needed there, since if $die_on_fail is false, false will be returned anyway and the $ok at that point is always false 18:02
But I'm hoping I'll be able to improve the code in that entire module and avoid this dance too.
AlexDaniel Zoffix: nice 18:03
MasterDuke re building docs. will whatever builds them automatically pull in new commits to Pod::To::Html?
Zoffix MasterDuke, nope 18:04
I can do it
MasterDuke cool, that should fix those links that end in _ 18:06
Zoffix MasterDuke, ==> Successfully installed Pod::To::HTML
dalek ast: 09c8d3f | LemonBoy++ | S12-enums/misc.t:
Tests for RT#129160 (#153)
 18:09
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=129160
TheLemonMan Zoffix, the only thing left to do is closing the ticket and calling it a day :D 18:10
Zoffix Way ahead of you ;)
BTW here you didn't miss anything. I've just marked the ticket as testsneeded that fast: irclog.perlgeek.de/perl6-dev/2016-0...i_13139757 18:12
TheLemonMan the RT ninja heh 18:13
mst is it a bird? is it a plane? no, it's madrussianexpatman! 18:16
Zoffix m: <pub no-pub>.pick.say 18:17
camelia rakudo-moar bdd469: OUTPUT«no-pub␤»
Zoffix m: <pub no-pub>.pick.say
camelia rakudo-moar bdd469: OUTPUT«pub␤»
Zoffix \o/
Zoffix &
ZoffixLappy I wonder if anyone uses the PERL6_TEST_TIMES in Test.pm6 anymore. I'm going to start with the assumption of "no" (in my rewrite-for-fun that might not land into nom) 18:43
mst ZoffixLappy: there is only 'pub' 18:47
ZoffixLappy :) 18:48
lizmat ZoffixLappy: fwiw, I wonder if we shouldn't generate Test.pm6 from a source with/without timing support 18:54
and if we want timing, we load the one with timing support
ZoffixLappy maybe 18:55
lizmat I mean, "use Test" is all about its exports anyway, so whether it actually comes from Test.pm6 is immaterial anyway
now to conditionally use one of two modules, that's actually something I don't see easily done (depending on a env var) 18:56
travis-ci Rakudo build passed. lizmat 'Merge pull request #869 from LemonBoy/enum-as-params 19:07
travis-ci.org/rakudo/rakudo/builds/157692999 github.com/rakudo/rakudo/compare/7...d4691e6a1a
jnthn MasterDuke: Left a comment on it. 19:15
TheLemonMan jnthn, maybe we need an unbox_u 19:18
because the _i value is rightfully decoded as negative
timotimo TheLemonMan: i don't think so, we just have to use the right _u ops whenever we work with that given register 19:22
jnthn TheLemonMan: That'd be one way to do the error checking, though as timo mentions we'd only end up turning it back to (native) signed int to feed it into the x op 19:27
TheLemonMan oh I see, I failed to check out the whole patch 19:32
dalek kudo/better-test-pm6: e03cac2 | (Zoffix Znet)++ | / (3 files):
Start possible de-spagettification of Test.pm6
 19:46
ZoffixLappy Coding at a bar doesn't really jive :)
ZoffixLappy starts writing something
mst I do it sometimes 19:47
usually I sit on IRC and read docs and kibbitz 19:48
dalek kudo/nom: 74f1edc | niner++ | src/core/CompUnit/PrecompilationUnit.pm:
Lazily deserialize the DependencySpecification of a PrecompilationUnit

Speeds up loading of GTK::Simple from 6.7 to 2.9 seconds as we shouldn't need the specification during an ordinary module load. It's only needed if we detect a change in the repositories.		 19:58
nine Now we're not reading any JSON and not EVALing any code during loading of a precompiled GTK::Simple :) 19:59
lizmat nine++ 20:00
ZoffixLappy wooo \o/ nine++
nine jnthn++ # profiler
tadzik++ # Qt GUI for the profiler with which I could actually read the profile 20:01
timotimo sorry about the problem with the html profiler :( 20:02
lizmat and another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2016/09/05/...ao-perl-6/ 20:22
dalek kudo/nom: a87fc7d | niner++ | src/core/CompUnit/PrecompilationStore/File.pm:
Cache path to the compiler in PrecompilationStoreFile

Speeds up loading of GTK::Simple from 2.9 to 2.5 seconds by saving about 1000 calls to .child.		 20:30
nine lizmat: it's now 8x :) from 20s on Saturday down to 2.5
lizmat Updated :-) 20:31
timotimo nine: i'm quite glad you're working on performance here :3
nine Unbelievable how much LHF there is... 20:32
lizmat well, anything related to $*SPEC is, really 20:33
one of the reasons I wanted to get rid of that in the first place
jnthn weekly \o/ 20:52
lizmat++
nine: Glad you put the profiler to good use :)
arnsholt has found a potential way to parse C headers without a completely ridiculous amount of work 20:56
Yet another item on the work queue...
dalek kudo/nom: e5d7a16 | niner++ | src/core/CompUnit/PrecompilationStore/File.pm:
Cache another layer of directories in PrecompilationStore::File

Saves another couple 100 calls to .child and speeds up loading GTK::Simple from 2.5 to 2.1 seconds. Caching the full .path however would lead to spectest regressions.		 21:00
ZoffixLappy :D
nine If it continues like this, I'm gonna have to make those measurements a bit more scientific...
But enough for today. Good night :) 21:02
ZoffixLappy night
lizmat nine: why {$compiler-id}{$precomp-id} instead of {$compiler-id ~ $precomp-id} ??
good night, nine
nine timotimo++ # reporting an excellent testcase 21:04
MasterDuke jnthn: a problem is that nqp::unbox_x goes negative before it complains about too wide bigints 21:05
*nqp::unbox_i
nine lizmat: no reason other than being tired :)
ZoffixLappy New blog post "Perl 6's Schrödinger-Certified Junctions": perl6.party/post/Perl-6-Schrodinger...-Junctions 23:08
cog__ lizmat++ 23:25

Powered by Cro and the Raku® Programming Language.

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

Thank you!