travis-ci Rakudo build errored. Zoffix Znet 'Add 4431bfb0a03 to changelog' 00:40
travis-ci.org/rakudo/rakudo/builds/153614594 github.com/rakudo/rakudo/compare/d...9da9928136
buggable ☢ [travis build above] Build log missing from at least one job. Check results manually. 00:41
Zoffix buggable, yup. You weren't lying! One job's log is missin' 00:52
japhb I'm getting a 'Malformed UTF-8' error trying to read binary output from a program using Proc::Async.new(...).stdout(:bin).tap({ ... }). Shouldn't that be impossible in :bin mode? 03:02
zostay are infix:< ≤ > and infix:< ≥ > deliberate omissions... i thought those had been implemented for some reason 04:41
there should be a ? in there some where
ShimmerFairy zostay: yeah, that's something I've never quite understood, IMO there's no reason they aren't there. 05:13
zostay in that case, perhaps i'll submit a patch and see if it sticks :) 05:15
the reason i can think of is just bloat since optimizing performance is a supreme goal, more details like this could work against that goal bit by bit 05:17
ShimmerFairy zostay: not a good argument though when even close to Christmas, you'd see e.g. Larry adding the Unicode version of a function composition operator. I think ≤ and ≥ are more acceptable than that :P . 05:18
zostay hehe 05:21
nine japhb: I would assume so, yes. 06:14
AlexDaniel zostay: gist.github.com/AlexDaniel/c89bd2786f9b63f31e4c 08:41
TheLemonMan the → is very nice 08:42
AlexDaniel I also like #← #↓ :) 08:43
Zoffix AlexDaniel, "It is a great looking operator, but unlike other ideas on this page it is not a 1-to-1 replacement." what do you mean a 1-to-1 replacement? 08:59
lizmat commute& 09:00
AlexDaniel Zoffix: → and -> are visually identical (well, sort of), but for example ~~ and ☺ are not :)
Zoffix huh
m: '☺'.uninames.say 09:01
camelia rakudo-moar 4674f1: OUTPUT«(WHITE SMILING FACE)␤»
AlexDaniel I mean, it's weird to suggest a character that looks differently
Zoffix ⌁ and ~~ look pretty similar
AlexDaniel what about ≈ ? :)
Zoffix i.imgur.com/S2h7bL7.png 09:02
AlexDaniel we can't use ≈, but it is a much closer match
okay-okay, I'll remove this statement :)
Zoffix ≤ ≥ ≠ are definitely something we want. They're just so awesome. 09:03
AlexDaniel Zoffix: by the way, what do you think about √ ∛ ∜ ? 09:05
Zoffix yey on √ and ney on others. 09:06
AlexDaniel Zoffix: but why? 09:07
Zoffix 'cause they are rarer than the 2 root. 09:08
AlexDaniel um… but… 09:09
🤷
Zoffix m: '🤷'.uninames.say
camelia rakudo-moar 4674f1: OUTPUT«(<reserved>)␤»
Zoffix No idea what that is 09:10
m: say 625⁰·²⁵
camelia rakudo-moar 4674f1: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Bogus postfix␤at <tmp>:1␤------> say 625⁰⏏·²⁵␤ expecting any of:␤ infix␤ infix stopper␤ postfix␤ statement end␤ statement modifier␤ …»
Zoffix heheh
AlexDaniel m: '🤷'.ord.base(16).say 09:11
camelia rakudo-moar 4674f1: OUTPUT«1F937␤»
Zoffix m: say 625**0.25
camelia rakudo-moar 4674f1: OUTPUT«5␤»
AlexDaniel Zoffix: unicode.org/emoji/charts/emoji-rele...html#1f937
Zoffix We should definitelly do the 🤦 too :P maybe a Unicode version of die()? XD 09:12
"FACE PALMdisbelief, exasperation, face, palm"
AlexDaniel face, palm :) 09:14
by the way, any plans on adding unicode 9.0 support to perl 6? 09:15
Zoffix Sure, just submit a PR ;) 09:21
Hm, harness6 all tests pass, but 'Heap corruption detected: pointer 0x7fc391e8aa20 to past fromspace' on second run 09:22
spacemen of the past corrupting my heaps!
AlexDaniel 🚀 09:23
m: say 2 <=> 10 09:25
camelia rakudo-moar 4674f1: OUTPUT«Less␤»
AlexDaniel m: say 2 🚀 10
camelia rakudo-moar 4674f1: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Confused␤at <tmp>:1␤------> say 2⏏ 🚀 10␤ expecting any of:␤ infix␤ infix stopper␤ postfix␤ statement end␤ statement modifier␤ statem…»
Zoffix 'Cannot call method 'Stringy' on a null object in method add-data at /home/cpan/CPANPRC/rakudo/lib/TAP.pm6 (TAP) line 281' 09:34
Looks like trying to debug the H6 is beyond my paygrade :/
dalek kudo/nom: 77da2dc | (Zoffix Znet)++ | docs/announce/2016.08.md:
Add 2016.08 release announcement
 10:00
kudo/nom: 37bf470 | (Zoffix Znet)++ | docs/release_guide.pod:
Update guide with 2016.08 now in the past
 10:05
kudo/nom: c201a76 | (Zoffix Znet)++ | tools/contributors.pl6:
Break up contributor list on multiple <80-char lines
 10:43
Zoffix goes for a nap 10:50
TheLemonMan whee, another bug squashed, this took way too much time 11:16
jnthn .tell Zoffix www.moarvm.org/releases/MoarVM-2016.08.tar.gz 12:15
yoleaux2 jnthn: I'll pass your message to Zoffix.
Zoffix \o/ 12:55
yoleaux2 12:15Z <jnthn> Zoffix: www.moarvm.org/releases/MoarVM-2016.08.tar.gz
dalek p: e368404 | (Zoffix Znet)++ | VERSION:
bump VERSION to 2016.08
 12:58
p: a714ed7 | (Zoffix Znet)++ | docs/release_guide.pod:
Remove dollar signs from shown shell commands

To make it easier to copy-paste them		 12:59
unmatched} lovely. started doing the release and my box died. screen frose and even reset button wasn't working and now bios is beeping on boot :( 13:11
Zoffix Wiggling the video card in its slot and staring intently at the box with a screwdriver in my hand seems to have solved the issue \o/ 13:20
dalek p: 2164ccc | (Zoffix Znet)++ | tools/build/MOAR_REVISION:
Bump MoarVM version to 2016.08
 13:47
kudo/nom: 2e963df | (Zoffix Znet)++ | tools/build/NQP_REVISION:
[release] bump NQP revision to 2016.08
 13:54
kudo/nom: 2dccd8c | (Zoffix Znet)++ | VERSION:
[release] bump VERSION to 2016.08
Zoffix 6.c-errata t/spec/S17-lowlevel/lock.t seems to be flopping. Fails about 20-30% of the time: gist.github.com/zoffixznet/b77605e...56a460cf11 14:17
TimToady wonders if we can subvert the npm ecosystem from the inside... 14:20
Zoffix release right-pad? 14:22
:)
TimToady just saw a keynote from the coo of npm, and they're doing a lot of things right 14:27
jnthn Zoffix: Oh...I fixed the rest on roast master, but forgot errata. It's the test at fault, not Rakudo.
TimToady though they're still unsure how they're going to get existing modules to coexist with es6 modules, which could have some bearing here with our js backend
Zoffix Ah
jnthn (I assuemd it was gonna be Rakudo or Moar to blame for ages, then when I eventually got around to looking at it, I realized it was a bust test and had it fixed in 10 minutes. D'oh. :)) 14:28
nwc10 the tag 2016.08 seems to be missing from the nqp github repository 14:29
mst sulks more about 6.c not getting lexical 'use'
nwc10 with the result that even nqp HEAD isn't "new" enough for rakudo HEAD 14:30
Zoffix nwc10, it was created about 44 minutes ago. Ensure you got the latest everything 14:31
github.com/perl6/nqp/releases/tag/2016.08
jnthn Was gonna ask if the tag somehow didn't get pushed, but if it's on GitHub... :) 14:32
jnthn away again for a bit
nwc10 very strange. because if I pull again in my nqp checkout I still don't see it 14:33
Zoffix Did you add --tags? it's git pull --tags or git fetch --tags or something like that
nwc10 Zoffix: correct. no I didn't. thanks 14:34
Zoffix \o/
nwc10 OK, why do I usually *not* need to do that?
aha er OK erk 14:35
| * commit 944cf37c95a0a8a5c9cfb45acec52953683d5eb2 (tag: 2016.08)
* commit 2164cccd0d72f2fc1472fdb8d9c85748277c0f35 (HEAD -> master, origin/master, origin/HEAD)
git log --graph --decorate origin/master 2016.08
[TuxCM] This is Rakudo version 2016.07.1-243-gc201a76 built on MoarVM version 2016.07-24-g31eccd7
csv-ip5xs 9.977
test 15.457
test-t 7.413
csv-parser 16.208
nwc10 show that it and master have diverged 14:36
Zoffix nwc10, what does that mean? 14:37
nwc10 the tag is for a commit which is not a parent of nqp master 14:38
I might not be able to explain it better than that 14:39
I hope that someone else is going to help me out here by explaining better
Zoffix Oh, I see what happened. 14:41
I bumped MoarVM version locally (and I think tagged too). On github fixed the release guide in the middle of that and pulled in those changes before pushing everything
Is that a problem or something?
nwc10 I think that soneone else is going to have to answer the "is tha ta problem" 14:43
but right now a `git describe` on nqp master gives a tag which is used for the nqp version which makes Rakudo think that the nqp is too old.
whilst nqp built from the tag is just fine
Zoffix Ah yeah, it gives `parrot-149-g2164ccc`. I think you have to run something else to get the right tag 14:44
As for 'makes Rakudo think'.... We're right in the middle of the release. Are you sure your Rakudo changes are latest and greatest?
I've just tested everything and it worked fine. 14:45
🎺🎺🎺📯📯📯📯📯📯🌈🌈🌈📦📦📦 14:48
The release of Rakudo #102 2016.08 has now been completed
🎺🎺🎺📯📯📯📯📯📯🌈🌈🌈📦📦📦
Zoffix celebrates with an appropriate amount of fun
nwc10 \o/
TheLemonMan define 'appropriate', do I have to wear pants ?
Zoffix .tell arnsholt I recall you mentioning you wanted to wait until after release to do the O-branch stuff. The release has now been done.
yoleaux2 Zoffix: I'll pass your message to arnsholt.
Zoffix TheLemonMan, well... I'm not wearing any :P 14:49
TheLemonMan Zoffix, that's the right spirit! 14:50
geekosaur git fetch --tags # ? 15:07
Zoffix Basically my botched tag means bumping nqp version for Rakudo will still be more involved than just `git describe` that we had to avoid since parrot tag and (possibly) more involved than the `git describe --match=20*` that gave the parrot tag. 'cause right now that gives reference against the 2016.07 release, like 2016.07-180-g2164ccc. 15:13
Luckily, Rakudo builds fine from the 2016.08 tag 15:14
mst you can always burn the tag with fire and replace it with a fixed one 15:15
the advantages may outweigh the risks
Zoffix mst, what are the risks? 15:16
mst people say "you can never replace a tag because people might just have already pulled it and then you'll confuse them" 15:17
I say "the sooner you replace it, the less people will get a botched tag"
Zoffix What will the confusion be?
Cause right now the HEAD is what the tag points to, except git describe doesn't see it, cause of my git pull --rebase stuff 15:18
jnthn, [Coke]_ , TimToady are you around? I made a booboo with the tag 15:19
mst what do you mean what will the confusion be 15:20
if you don't actually see a problem, just replace the tag with a fixed on already
Zoffix Well, you said 'and then you'll confuse them'. What do you mean? What are the ramification of replacing the tag?
Yeah, but I don't see a problem because I'm an ignorant idiot.... 😜 15:21
AlexDaniel
.oO( just don't do whatever was done with 2016.01 and 2016.01.1 … it makes bisectable freak out )
 15:28
Zoffix I was away at that time, so I don't know what happened. 15:29
And Rakudo wouldn't need to be retagged.
Hm, I guess yeah, couldn't we just add a 2016.08.1 tag to nqp?
AlexDaniel Zoffix: if I recall correctly, 2016.01 and 2016.01.1 are hanging in the breeze, which means that there's no real path from 2016.01 to HEAD. That's OK, but it makes things with whateverables a bit more painful 15:33
dalek p: d50296e | LemonBoy++ | src/vm/moar/QAST/QASTOperationsMAST.nqp:
Simplify the compilation of 'if' switches.

Optimize the case where there's no else branch by not emitting a goto. Also, remove some other code that's being generated but is actually unreachable.		 15:37
p: ca75b3e | (Paweł Murias)++ | src/vm/moar/QAST/QASTOperationsMAST.nqp:
Merge pull request #305 from LemonBoy/simpler-if

Simplify the compilation of 'if' switches.
TheLemonMan I've updated nqp's #170, nqp ninjas please have a look if you can :) 15:40
Zoffix OK. I'm going against replacing the tag. 15:43
And wait for other devs to come in and then we'll figure out if we need to create 2016.08.1 on nqp or what. 15:44
arnsholt Zoffix: Cheers! 15:58
yoleaux2 14:48Z <Zoffix> arnsholt: I recall you mentioning you wanted to wait until after release to do the O-branch stuff. The release has now been done.
arnsholt TheLemonMan: If the Rakudo spectests pass with your tweaked NQP it's probably fine, but this one is deep enough that I think jnthn should probably weigh in on it 15:59
I'm also curious, what (if anything) changes if the result of the block *is* used?
TheLemonMan arnsholt, the codegen's different because the protected block knows the result's gonna be used 16:03
TheLemonMan & 16:06
pmurias .tell TheLemonMan the protected block *is* always generated as if it's result was gonna be used 16:16
yoleaux2 pmurias: I'll pass your message to TheLemonMan.
ugexe github.com/rakudo/rakudo/blob/nom/...th.pm#L422 # Is JVM dir() broken here? . and .. are both default values of :$test fwiw, but then :$test is matched against the . and .. for some reason? 16:23
none(<. ..>) are the default values rather
Zoffix m: dd[ $*VM.version, $*PERL.compiler.version ] 16:53
camelia rakudo-moar c201a7: OUTPUT«block <unit>␤Method 'Int' not found for invocant of class 'Version'␤ in block <unit> at <tmp> line 1␤␤»
Zoffix m: dd [ $*VM.version, $*PERL.compiler.version ]
camelia rakudo-moar c201a7: OUTPUT«[v2016.07.24.g.31.eccd.7, v2016.07.1.243.gc.201.a.76]␤»
Zoffix oh crap 16:54
Oh. I guess camelia doesn't build every commit right away. Never mind.
s: dd $*VM.version, $*PERL.compiler.version 16:59
SourceBaby Zoffix, Something's wrong: ␤ERR: v2016.07.24.g.31.eccd.7␤v2016.07.1.243.gc.201.a.76␤Cannot resolve caller sourcery(Nil); 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 gets a bad feelingh
dalek ast: ec5b901 | usev6++ | S01-perl-5-integration/ (2 files):
Skip Perl 5 integration tests if requirements not met

  (similar to other Perl 5 integration)		 17:07
ast: 840a2ee | usev6++ | S (3 files):
Fudge some new tests for rakudo-j
Zoffix <Zoffix> OK. I'm gonna do a 2016.08.1 'cause I'm not 100% sure just changing the tag will fix everything and won't introduce new problems. 17:12
dalek p: 0634db8 | (Zoffix Znet)++ | VERSION:
bump VERSION to 2016.08.1
 17:42
p: fdbebad | (Pawel Murias)++ | / (2 files):
Fix issue #170. Exact cause and location of the bug found by LemonBoy++.
 17:50
kudo/nom: 26ebe43 | (Zoffix Znet)++ | tools/build/NQP_REVISION:
[release] bump NQP revision to 2016.08.1

The 2016.08 tag is botched and users who pull changes into older repositories do not get it and the build fails.		 17:55
ast: 052d5cb | usev6++ | S (2 files):
Unfudge passing test for rakudo-j
 18:04
kudo/nom: f372635 | (Zoffix Znet)++ | docs/announce/2016.08.1.md:
Add 2016.08.1 Release Announcement
 18:14
kudo/nom: a07a2e1 | (Zoffix Znet)++ | VERSION:
[release] bump VERSION to 2016.08.1
Zoffix Bah. Sitting here, waiting... ran TEST_JOB=30 make spectest (no 'S' on jobs) 18:42
Well, this was fun. 18:51
Off to the pub... Gonna squeeze out a blog post from all this :) 18:52
b2gills TimToady: I just noticed that ｢(1..3).minmax｣ returns a list, while every other minmax sub/operator/method that I looked at returns a Range, is this intentional? ( I was thinking adding min/max/minmax to the ｢[+] Range｣ optimization ) 19:25
TimToady hmm 19:39
lizmat waves from Bratislava 19:40
b2gills: Range.minmax should return a Range
timotimo o/ lizmat 19:41
[TuxCM] waves from Cluj
b2gills waves from Waverly ( The one in Iowa ) 19:43
DrForr Weird, I'm in Cluj too. 19:49
mst flies out tuesday 19:55
ok, so, not sure if this is the right place to be asking but
ZoffixLappy has little Cluj what this is all about....
mst both rakduo and star repositories have a Configure.pl
ZoffixLappy YAPC::EU I'm guessing...
mst they appear to be mostly the same code
yes 19:56
ZoffixLappy \o/
mst do we have any idea how forward/backporting patches is handled?
lizmat mst: not sure... 19:59
long term, I think the plane is to have a Configure.nqp 20:00
*plan
mst lizmat: that's not what I mean
what I mean is, "how do changes get propagated between the two NOW"
lizmat ah... in that case: no idea 20:01
mst right
lizmat moritz might know, but he's out roaming
mst the more I read this build system the more I suspect nobody working on it ever had any idea
lizmat mst: the way I understand it is was only built that way to get things working 20:02
so I guess now would be a good time to work on it more :-)
mst yes. but if nobody can even tell me which copy to make patches against
that becomes trickier than I'd like
I am trying to make this not amateur hour. I just need a little more information. 20:03
lizmat moritz FROGGS masak (in that order) would be the people I'd check this with
pmichaud might also know
ZoffixLappy FWIW, I recall making Perl 5.10-compat changes to Rakudo's Configure.pl that I never propagated to Star's 20:04
mst the release guide doesn't mention it
mst checks log/blame instead
ZoffixLappy This in particular: github.com/rakudo/rakudo/commit/a3...432a45d219
timotimo i've already wondered in the past about why we have two slightly different copies of the whole configure shebang 20:05
mst seems like -some- stuff has been merged down into star from the submodule
but not all
meanwhile, the Makefile template is also a problem 20:06
but at least that comes straight in from rakudo
travis-ci Rakudo build errored. Zoffix Znet '[release] bump VERSION to 2016.08.1' 20:07
travis-ci.org/rakudo/rakudo/builds/153823835 github.com/rakudo/rakudo/compare/f...7a2e173cfc
buggable ✓ [travis build above] One job failed due to the timeout. No other failures.
lizmat b2gills: hmmm... it appears there are quite some spectests that expect Range.minmax to return a List :-( 20:10
b2gills Range.min-and-max 20:11
ZoffixLappy lizmat, are they also in 6.c-errata? Maybe they were added as part of testing bug fixes for unrelated stuff. I know I added a few and may have assumed the returned List was the expected thing to return 20:13
lizmat ZoffixLappy: I probably fell into that same trap :-(
mst can anybody see a downside to my just saying 'fuck it' and ignoring star and focusing on fixing rakudo mainline? 20:17
lizmat mst: that you might have to do it for Rakudo star as well ? 20:18
ZoffixLappy mst, I don't. IMO the whole Star thing needs to be rethought.
b2gills mst: If it is the difference between you working on it, and you not working on it. I choose you working on it.
mst well, I have to patch one of the two almost identical scripts first. 20:19
nobody knows how the changes are propagated
or even if there's a plan for that
ZoffixLappy :)
mst and it *looks* like start's Configure.pl gets stuff merged down from rakudo's via the submodules
b2gills I doubt that any changes are propagated
mst b2gills: nah, *some* of them are
it's great
b2gills mst: have an appropriate amount of masochistic fun 20:20
mst lizmat: I think setting fire to star's copypasta and doing it properly would be better tbh
I *think* basically it's supposed to get merged, but people only remember sometimes 20:21
lizmat
.oO( hmmmm.... fire on a hot summer night )
mst and there's nothing in the release manager docs
lizmat mst: I think that's probably true 20:22
mst I think turning the star-specific bits into a patch
lizmat mst++
mst and modifying the release automation to apply the patch to rakudo's configure.pl
would be a better plan
in which case, fixing rakudo's first becomes obviously correct
lizmat mst: agree 20:32
mst hm. this is going to be less horrible than I thought 20:33
the HURR DURR EVERYTHING MUST HAVE SAME PREFIX stuff is isolated to a couple places
lizmat mst: maybe the people that did this did have some clue? :-) 20:38
mst lizmat: they made something moderately well factored that works on all of their machines, with their chosen configure options 20:39
hmf. additional question: where do the moar tarballs live? 20:41
ZoffixLappy mst, www.moarvm.org/releases/ may be one of the possible answers :) 20:43
mst yay
lizmat m: my $r = 1..5; my @r = $r; dd @r # this feels wrong in light of: 20:56
camelia rakudo-moar a07a2e: OUTPUT«Array @r = [1..5,]␤»
lizmat m: my @r = 1..5; dd @r 20:57
camelia rakudo-moar a07a2e: OUTPUT«Array @r = [1, 2, 3, 4, 5]␤»
lizmat jnthn TimToady : ^^^ opinions ?
ZoffixLappy Feels right to me. I'm asking a Range to be stored in a "single item." so it stores the range 20:58
Same as with my $r = 1, 2, 3; doesn't work the same as my @r = 1, 2, 3
m: my $r = 1, 2, 3; my @r = 1, 2, 3; dd[ $r, @r ] 20:59
camelia rakudo-moar a07a2e: OUTPUT«WARNINGS for <tmp>:␤Useless use of constant integer 2 in sink context (lines 1, 1)␤Useless use of constant integer 3 in sink context (lines 1, 1)␤block <unit>␤»
ZoffixLappy m: my $r = 1, 2, 3; my @r = 1, 2, 3; dd [ $r, @r ]
camelia rakudo-moar a07a2e: OUTPUT«WARNINGS for <tmp>:␤Useless use of constant integer 2 in sink context (lines 1, 1)␤Useless use of constant integer 3 in sink context (lines 1, 1)␤[1, [1, 2, 3]]␤»
mst lizmat: are the rakudo+nqp+moarvm releases for start chosen because they're unusually stable, or is it just "don't make a new star too often" ?
lizmat a star release is always dependent on a stable Moar/NQP/Rakudo combo, afaik 21:00
this may be a .1 point release if we find something wrong just after a compiler release
like we had with 2016.08 / 2016.08.1 right now
so a Rakudo Star would probably depend on 2016.08.1 21:01
jnthn lizmat: I don't see anything wrong there.
mst right, then I think I'll stick to using the set of tarballs shipped with the last star for the moment
jnthn (For the reason ZoffixLappy stated)
mst and eat the necessity of maybe tweaking my patches to apply to master
lizmat m: say (3.5e1 .. 4.5e1).Str # jnthn ZoffixLappy 21:02
camelia rakudo-moar a07a2e: OUTPUT«35 36 37 38 39 40 41 42 43 44 45␤»
lizmat then this looks wrong to me...
ZoffixLappy m: say $(3.5e1 .. 4.5e1).Str 21:03
camelia rakudo-moar a07a2e: OUTPUT«35 36 37 38 39 40 41 42 43 44 45␤»
ZoffixLappy m: say ($(3.5e1 .. 4.5e1)).Str
camelia rakudo-moar a07a2e: OUTPUT«35 36 37 38 39 40 41 42 43 44 45␤»
ZoffixLappy shrugs
May be
lizmat I'm about to change this to:
$ 6 'say (3.5e1 .. 4.5e1).Str'
35e0..45e0
but that breaks some tests... which depended on the above dubious Stringification 21:04
b2gills Range is a Positional, so I can see .Str doing the same as Array.Str 21:06
jnthn lizmat: I'm a bit tired for having a well-considered opinion on that, but I'd say it's one to filter through TimToady++ 21:07
pmurias jnthn: it would be great if you had a quick look at the fdbebadd1dbffddc470511a04bfb7f859cb276bb commit in nqp, as I'm not 100% it's the right way to fix that 21:10
TimToady we intentially made array init follow the one-arg rule
jnthn TimToady: I was talking about the .Str of Range one. The one-arg rule array is plenty clear (to me :)). 21:11
pmurias: I'm...curious why it's needed 21:12
TimToady oh, I think it's correct to expand under Str
Str is not gist
lizmat m: sub a(@a) { say @a.perl }; a 1..5; my $r = 1..5; a $r # here there's no difference
camelia rakudo-moar a07a2e: OUTPUT«1..5␤1..5␤»
jnthn pmurias: It looks like a register leak too
lizmat m: my @r = 1..5; say @a.perl 21:13
camelia rakudo-moar a07a2e: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Variable '@a' is not declared␤at <tmp>:1␤------> my @r = 1..5; say ⏏@a.perl␤»
jnthn $protil.result_reg is never released, bloating the number of needed registers
lizmat m: my @r = 1..5; say @r.perl
camelia rakudo-moar a07a2e: OUTPUT«[1, 2, 3, 4, 5]␤»
TimToady Str is not Perl either
Str is for printing things out to a line printer
jnthn Ah, right. Makes sense.
lizmat m: my $rt = 1..5; my @r = $r; say @r.perl 21:14
camelia rakudo-moar a07a2e: OUTPUT«===SORRY!=== Error while compiling <tmp>␤Variable '$r' is not declared. Did you mean '@r'?␤at <tmp>:1␤------> my $rt = 1..5; my @r = ⏏$r; say @r.perl␤»
lizmat m: my $r = 1..5; my @r = $r; say @r.perl
camelia rakudo-moar a07a2e: OUTPUT«[1..5,]␤»
lizmat the behaviour of my @r = $r / 1..5 seems inconsistent with a($r) / a(1..5)
jnthn That has to be right, in so far as `my @r = $any-Scalar-here` we'd expect to behave as a single item 21:15
Nope
They're not the same thing
= is assignment
we *bind* signatures
lizmat ah, good point :-)
yup, ok
then I need to fix some tests
because the tests don't really test the right thing :-) 21:16
jnthn :) 21:18
El_Che lizmat: nxadm.wordpress.com/2016/08/20/ple...x-checker/ 21:19
lizmat El_Che++
El_Che I should reread the damn thing to get spelling errors out :)
dalek ast: 6ac1ea3 | lizmat++ | S02-types/range.t:
Fix some Range checks

They were dependent on potentially incorrect Stringification.		 21:29
ast/6.c-errata: 4258f6d | lizmat++ | S02-types/range.t:
Fix some Range checks

They were dependent on potentially incorrect Stringification.		 21:32
kudo/nom: 5a4ec53 | lizmat++ | src/core/Baggy.pm:
Make MMD lookup handle Baggy.ACCEPTS
 21:57
lizmat good night, #perl6-dev! 22:22
ZoffixLappy night
jnthn 'night, lizmat o/
travis-ci Rakudo build passed. Elizabeth Mattijsen 'Make MMD lookup handle Baggy.ACCEPTS' 22:50
travis-ci.org/rakudo/rakudo/builds/153851119 github.com/rakudo/rakudo/compare/a...4ec53421a7
dalek kudo/nom: ee621d1 | dmaestro++ | lib/Test.pm6:
There is no 'done', only 'done-testing'

Clean up a few places done (obsolete) or done_testing (perl 5 legacy) were used in the comments.
kudo/nom: 668dc5c | lizmat++ | lib/Test.pm6:
Merge pull request #843 from dmaestro/prune_references_to_obsolete_done

There is no 'done', only 'done-testing'
El_Che lizmat: I don't know if this is weekly material, but here it goes: nxadm.wordpress.com/2016/08/21/vim...-6-editor/ 23:18
AlexDaniel
.oO( Perl 6 as a Vim editor… )
 23:19
El_Che hehe 23:20
ZoffixLappy New blog post: "I Botched a Perl 6 Release And Now a Robot Is Taking My Job": perl6.party/post/I-Botched-A-Perl-6...ing-My-Job 23:31
timotimo hah :D 23:51
ZoffixLappy :)

Powered by Cro and the Raku® Programming Language.

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

Thank you!