stmuk Sounds like having R* 2017.05 off a more stable monthly release is a good idea although I'll probably build a testing one based on 04.x (without official release) to try out things anyway 07:14
yoleaux 22 Apr 2017 10:29Z <Zoffix> stmuk: R* likely delayed you say... I'm thinking of maybe delaying it by 4 weeks and cutting it off 2017.05 or something isn't a bad idea. There are two pretty serious bugs in 2017.04.2 that we'd need to patch or point-release for
samcv stmuk, let me know how testig one goes 07:30
though idk are there other bugs other than the regex bug i just fixed? i actually don't know what the other point releases were cut for 07:31
samcv reads changelog on rakudo repo
oh i see now 07:32
lizmat Files=1191, Tests=56827, 203 wallclock secs (12.15 usr 4.80 sys + 1197.53 cusr 119.23 csys = 1333.71 CPU) 07:42
samcv lizmat, can you tell me about radix?
lizmat not much more than what I know when looking at the code now 07:43
samcv the nqp op and its return values. see what i just said in #moarvm about plans for the indexic op. since we need to return more data to nqp/rakudo than only the index of the located match
github.com/perl6/nqp/blob/master/d...down#radix
m: use nqp; my str $thing = '10'; say nqp::radix(10, $thing, 0, 0) 07:44
camelia (10 100 2)
samcv not sure. it says the that 100 is the radix ** (number of digits converted) 07:45
i would think it'd have converted 2 digits, and it would be at offset 2 (which is the last number)
so i expected 10, 2,2
but maybe i'm reading the doc wrong
Geth rakudo/nom: 22bd2bbd7a | MasterDuke17++ | src/core/Main.pm
Escape spaces and quotes in MAIN() usage message

Before, if you had a literal parameter in a MAIN() with a space or quote (single or double) the parameter wouldn't get quoted when a usage message was printed. This means you couldn't just copy what was suggested. Now, qoute if needed.
Fixes RT #113954		 07:46
samcv m: use nqp; my str $thing = ' 10'; say nqp::radix(10, $thing, 1, 0)
camelia (10 100 3)
rakudo/nom: f9ebd24666 | lizmat++ (committed using GitHub Web editor) | src/core/Main.pm
Merge pull request #1064 from MasterDuke17/escape_spaces_and_quotes_in_usage_message

Escape spaces and quotes in MAIN() usage message
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=113954
samcv m: use nqp; my str $thing = '99'; say nqp::radix(10, $thing, 0, 0)
camelia (99 100 2)
samcv but maybe it's just the radix ** 2 07:47
since i see the ** in the docs, but. that's not super clear
ohhh i get it. ok. it relates to the highest decimal place it parsed 07:48
m: use nqp; my str $thing = '1000.0'; nqp::radix(10, $thing, 0, 0)
camelia ( no output )
samcv m: use nqp; my str $thing = '1000.0'; say nqp::radix(10, $thing, 0, 0)
camelia (1000 10000 4)
samcv m: use nqp; my str $thing = '1000'; say nqp::radix(10, $thing, 0, 0)
camelia (1000 10000 4)
samcv m: use nqp; my str $thing = '1'; say nqp::radix(10, $thing, 0, 0)
camelia (1 10 1)
Geth nqp: 61b9a2da82 | (Samantha McVey)++ | docs/ops.markdown
[ops.markdown] make radix doc a little more clear

Was not entirely clear that the words inside stood for a variable which was the number of digits converted and not human language grammatical ones. Make it more clear.		 07:53
[Tux] This is Rakudo version 2017.04.2-28-gf9ebd2466 built on MoarVM version 2017.04-44-gf0db8822 09:02
csv-ip5xs 3.221
test 13.123
test-t 5.262 - 5.336
csv-parser 13.096
Zoffix samcv: whatisit? 09:49
samcv oh. if we're making a point release. the changes are in rakudo
for the regex thing 09:50
doesn't have to be today, but would be nice if there were a point release. but idk other people think maybe it's not a good idea.
Zoffix wtf is happening with test-t 09:51
buggable: speed 10
buggable Zoffix, ā–ā–†ā–‚ā–„ā–ƒā–ƒā–ƒā–‚ā–„ā–ƒ data for 2017-04-20ā€“2017-04-23; range: 5.102sā€“5.479s; 3% slower
Zoffix buggable: speed 20
buggable Zoffix, ā–‚ā–ā–ƒā–ƒā–ƒā–ƒā–ƒā–ƒā–„ā–ƒā–ƒā–ˆā–„ā–†ā–„ā–„ā–„ā–„ā–†ā–… data for 2017-04-15ā€“2017-04-23; range: 4.994sā€“5.479s; 4% slower
Zoffix buggable: speed 30
buggable Zoffix, ā–ā–‚ā–„ā–„ā–‚ā–ƒā–‚ā–ƒā–ˆā–…ā–‚ā–‚ā–„ā–ƒā–„ā–ƒā–ƒā–ƒā–„ā–ƒā–ƒā–ˆā–„ā–†ā–…ā–…ā–…ā–„ā–†ā–… data for 2017-04-11ā€“2017-04-23; range: 4.942sā€“5.479s; 6% slower
Zoffix buggable: speed 40
buggable Zoffix, ā–‚ā–‚ā–‡ā–ā–‡ā–ƒā–‡ā–ā–‚ā–ā–ā–‚ā–„ā–„ā–‚ā–„ā–‚ā–ƒā–ˆā–…ā–‚ā–‚ā–„ā–ƒā–„ā–„ā–ƒā–ƒā–„ā–ƒā–ƒā–ˆā–„ā–†ā–…ā–…ā–…ā–„ā–†ā–… data for 2017-04-07ā€“2017-04-23; range: 4.921sā€“5.479s; 6% slower
samcv buggable, speed 200 09:52
buggable samcv, Refusing to do more than 100 last entries
samcv buggable, speed 100
buggable samcv, ā–ā–‚ā–ā–ā–ƒā–‚ā–‚ā–‚ā–‚ā–‚ā–ā–ā–ˆā–‚ā–‚ā–ƒā–ā–ā–ā–ā–ā–ā–ā–ā–ā–ā–ā–ā–ā–‚ā–ā–ā–ā–‚ā–‚ā–ā–ā–ā–ā–ā–ā–…ā–‚ā–ā–ā–ā–ā–ā–ā–ā–‚ā–ā–ƒā–ā–‚ā–ā–ā–ā–ā–ā–ā–ā–‚ā–ā–‚ā–‚ā–‚ā–ā–ā–ā–ā–ā–‚ā–‚ā–ā–‚ā–ā–‚ā–ƒā–‚ā–‚ā–ā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ā–ƒā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ā–‚ data for 2017-03-09ā€“2017-04-23; range: 4.829sā€“7.664s; 5% slower
Zoffix samcv: the other bug there weren't a point release for was somethign about <( )> and action methods. 09:53
NeuralAnomaly: release
oops
timotimo haha
samcv NeuralAnomaly, status
NeuralAnomaly samcv, [āœ˜] Next release will be in 3 weeks and 6 days. Since last release, there are 7 new still-open tickets (5 unreviewed and 0 blockers) and 45 unreviewed commits. See perl6.fail/release/stats for details
Zoffix Well, even if my VM were up, it's in safemode mode anyway :)
samcv but my reasoning is regex is something a new user might try out, and if they try it out and it's broken 09:54
it would not be very good of an experience. but the other stuff i guess were problems too. but
that's just my opinion
Zoffix samcv: I'd expect the user to use Rakudo Star. Not a tagged rakudo release.
Or rakudobrew, where it's also fixed
samcv in moar-blead? 09:55
or?
Zoffix m: say "abc" ~~ m:i/caaaaa/
camelia False
Zoffix Rakudo HEAD
Default `rakudobrew build moar` gets EHAD
samcv how does that work. also some distros go off our tagged releases i think
oh
and moar-blead?
that's git moar and git rakudo?
Zoffix You know what. I'm just gonna cut a point release right now. 09:56
samcv k :)
timotimo oh? things are good? 10:00
Zoffix What things?
Gonna test out the whole "make a branch for release; cherry pick; tag it; then delete it" thing. 10:01
timotimo oh 10:03
Zoffix c: 2017.03 say 'a' ~~ m:i/ab/ 10:08
committable6 Zoffix, Ā¦2017.03: Ā«ļ½¢aļ½£Ā»
Zoffix Oh so it's not a new bug?
c: 2017.03 say 'abcdb' ~~ m:i/ab/ 10:09
committable6 Zoffix, Ā¦2017.03: Ā«ļ½¢abļ½£Ā»
Zoffix There's a problem with 'delay release by a month' thing I proposed. Well, kind'f. You can't use that branch to release off roast master. You'd have to check out a commit around the time of last commit to release branch, otherwise you'll have failures. 10:14
And if you cherry pick some fixes into it, you'll have even more failures :|
dogbert17 o/ 10:20
stupid question of the day
does nqp::die write its output to stdout and if so why? 10:21
timotimo it does not
it throws an exception
dogbert17 so where's the exceptions text written then?
timotimo whatever handler catches it 10:22
dogbert17 looking a bit at RT #130760
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=130760
timotimo probably the one in Perl6::Compiler if you don't do anything to catch it yourself
could very well be that the standard exception handler isn't even in scope when that exception gets thrown 10:24
Zoffix dogbert17: there's a `say` for usage: github.com/rakudo/rakudo/blob/nom/...er.nqp#L81
dogbert17 looks 10:25
would it be possible to use 'note' instead? 10:26
Zoffix REMINDER: The proper TAP.pm6 now lives in github.com/perl6/tap-harness6 10:28
timotimo yeah, but it should only use note if the usage is printed because of an error
i.e. perl6 --help should go to stdout
dogbert17 timotimo: agreed
Geth tap-harness6: 6e6dc5292f | timo++ (committed using GitHub Web editor) | lib/TAP.pm
port fix for file descriptor exhaustion from rakudo

it used to not close the stdout descriptors for subprocesses, thus easily reaching multiple thousand open file descriptors		 10:30
tap-harness6: 4ff82b1d86 | (Zoffix Znet)++ | lib/TAP.pm
Close IO::Hadle/IO::Pipe when done reading
 10:34
tap-harness6: c19f5cc8d9 | (Zoffix Znet)++ | .gitignore
Ignore precomp files
rakudo/2017.04.3-release: 5 commits pushed by TimToady++, (Zoffix Znet)++, (Timo Paulssen)++, (Samantha McVey)++ 10:35
Zoffix timotimo: "bump nqp for eqatic fix" what was the issue? 10:39
samcv this is the same thing
Zoffix Ah ok
samcv yea
that actually was the indexic fix that he bumped. then i did equatic fix
but timo wrote the wrong op in the name of the commit 10:40
but regardless. both ops are now rescued
Geth rakudo/2017.04.3-release: b4455d875c | (Zoffix Znet)++ | docs/ChangeLog
Log changes for 2017.04.3 release
 10:41
timotimo yes, i did it totally wrong 10:43
i wonder if we should start using git notes for that kind of thing
samcv what are git notes 10:52
Geth rakudo/2017.04.3-release: 147ad2ea91 | (Zoffix Znet)++ | docs/announce/2017.04.3.md
Add 2017.04.3 release announcement
rakudo/2017.04.3-release: a4e59cf3b2 | (Zoffix Znet)++ | VERSION
[release] bump VERSION to 2017.04.3
 10:53
samcv yay more versions
timotimo samcv: sort of a thing you can attach to a commit "after the fact"
samcv oh
timotimo the ownership is reversed, so that the commit content doesn't have to change 10:54
samcv well i describe it fully in moarvm commit log
idk. ok i see
timotimo i could have put a note in saying "oops my commit message was crap"
definitely beats force-pushing over master
Zoffix just comments on the commit in github in those cases...
samcv i should try out git notes 10:55
timotimo i have not used them yet 10:59
and i don't know of anybody who has
more or less just a random thought
samcv i'll try it out sometime on a private repo and see what happens
i gotta go, may not be back before i go to sleep 11:00
Zoffix m: say 'ļ¬†a' ~~ m:i/st/ 11:01
camelia ļ½¢ļ¬†aļ½£
Zoffix c: 2017.01,2017.02 say 'ļ¬†a' ~~ m:i/st/
committable6 Zoffix, Ā¦2017.01,2017.02: Ā«FalseĀ»
Zoffix c: 2017.03,2017.04 say 'ļ¬†a' ~~ m:i/st/ 11:02
committable6 Zoffix, Ā¦2017.03,2017.04: Ā«ļ½¢ļ¬†aļ½£Ā»
Zoffix So that's another regression :/
Ah no
just works differently but still brokenly
samcv yeah that's going to be an issue until i retrofit indexic/eqatic ops 11:03
dogbert17 timotimo: using note works, the question then is what's the best way to figure out wheather 'note' or 'say'. Looking at the string parameter sent to the 'usage' method feels a bit brittle. Any suggestions?
samcv to return information about the length of the expansion
since atm it has no clue those cp's expanded and thinks the needle of 2 graphemes will hae matched a 2 grapheme section of string 11:04
that is next on the list
dogbert17 s/wheather 'note'/wheather to use 'note'/
timotimo dogbert17: where does it decide that an error should be displayed? 11:05
samcv well i have eqatic somewhat working. but. need changes in regex compiler to have it do things
timotimo like "unknown flag: --foobar"
samcv night o/
happy point release tidings to you and your kin
Zoffix night 11:06
timotimo night samcv
dogbert17 timotimo: not sure but I belive it might be in the class HLL::CommandLine::Parser found in nqp/src/HLL/CommandLine.nqp 11:07
that's where I found the string 'No such option' 11:08
timotimo we can introduce some API for that
does that function call the usage function?
dogbert17 that's the problem (for me) I can't find that place, if it does it is not obvious to me :( 11:09
timotimo let me see 11:10
ok, it just dies
aha 11:13
nqp/src/HLL/Compiler.nqp 11:14
dogbert17 what have you found
timotimo line 333
it has a try with .parse in it, when it CATCHes, it calls usage
dogbert17 nice find
is there a way to figure out if usage has been called from that code or is that the wrong approach? 11:15
timotimo we could set a dynamic variable 11:17
dogbert17 something like $*CALLED-FROM-EXCEPTION ? 11:18
timotimo i wouldn't call it that :) 11:23
dogbert17 :)
timotimo $*USAGE-FOR-FAILURE?
dogbert17 naming is one of the hardest things ...
Geth rakudo: zoffixznet++ created pull request #1065:
2017.04.3 release		 11:25
Zoffix Well, release is done, but do I merge the branch or what? 11:26
c: 2017.04.3 say "wut" 11:27
committable6 Zoffix, Ā¦2017.04.3: Ā«No build for this commitĀ»
Zoffix git describe 11:30
2017.04.2-28-gf9ebd24
That's off a fresh clone. Gonna merge and see, I guess
timotimo what did i get put into the contributors list for? for the bump commit? :) 11:31
Zoffix I guess 11:32
dogbert17 or your TAP.pm6 fix 11:33
Zoffix It's not in release
dogbert17 ah
timotimo i don't really understand what "whenever MATCH is called" means in the fix comment
Geth rakudo/nom: 9 commits pushed by TimToady++, (Zoffix Znet)++, (Timo Paulssen)++, (Samantha McVey)++ 11:34
Ā¦ rakudo/nom: version bump brought these changes: github.com/perl6/nqp/compare/2017....2-ga5337ff 11:35
timotimo huh
2017.04 was 12:13 am, 2017.04.1 was 11:59 am?
how did that happen 11:36
Zoffix By releasing within 6 hours? 11:37
12
12:13am is midnight; 11:59am is noon 11:38
c: $*PERL.compiler.version 11:39
committable6 Zoffix, I cannot recognize this command. See wiki for some examples: github.com/perl6/whateverable/wiki/Committable
Zoffix c: HEAD $*PERL.compiler.version.say 11:40
committable6 Zoffix, Ā¦HEAD(f9ebd24): Ā«v2017.04.2.28.gf.9.ebd.2466Ā»
Zoffix .tell stmuk well, 2017.04.3 did happen after all. Should be OK to base R* off of, if needed
yoleaux Zoffix: I'll pass your message to stmuk.
timotimo m( 11:41
this time format is simply ridiculous 11:42
how can anybody ever think it's a good idea to keep this garbage
Zoffix is used to it
ZOFFLOP: t/spec/integration/advent2012-day15.t # 6.c-errata version 11:51
m: say 19/365 11:54
camelia 0.052055
Zoffix In the past year, I took a break for only 5% of days, according to my github contributions chart :|
timotimo yikes 11:57
get yourself a little bit of vacation some time :)
Zoffix Today's as good a time as any, I guess 12:01
Zoffix & for rest of the day :)
timotimo \o/ 12:02
have a good one!
dogbert17 Zoffix: play some games
timotimo don't you dare come back before you're relaxed ;) ;)
dogbert17 timotimo: this dynamic variable we spoke about, doesn't it have to be declared in two places? 12:03
timotimo nah, we'd just check if it exists (with a try, probably) when we output the usage
oh hold on
this is a method we're talkin gabout 12:04
why not just pass a named parameter
that way other users of HLL::Compiler don't have to change for this
dogbert17 that sounds too easy :)
but clever
Zoffix ZOFVM: Files=1241, Tests=133802, 121 wallclock secs (23.86 usr 3.43 sys + 2531.13 cusr 130.78 csys = 2689.20 CPU) 12:07
dogbert17 could you send an appropriate output handle as a named param and then use that when outputting or should we settle for a boolean? 12:09
timotimo i think boolean is enough 12:11
dogbert17 ok, can try to cobble something together when I get back from a short errand & 12:12
unless you want to do it of course
timotimo i'm working on something else right now :) 12:13
dogbert17 cool, will try to fix it in a bit then :)
Geth star: d45c907fb8 | (Steve Mynott)++ | tools/star/Makefile
Increase Rakudo a point version to .3
 13:20
stmuk Zoffix: is there going to be a nqp-2017.04.1.tar.gz release based on 2017.04-24-g87501f7b? 13:23
yoleaux 11:40Z <Zoffix> stmuk: well, 2017.04.3 did happen after all. Should be OK to base R* off of, if needed
Zoffix uuuhhhhh 13:24
shit >_<
stmuk I think it's only needed by star anyway and a usual rakudo build uses a git checkout of nqp so maybe its just a case of sticking that tarball up and not changing rakudo 13:30
Zoffix stmuk: what about packagers and stuff? You now can't build 2017.04.3 rakudo without fetching stuff over net 13:31
stmuk I don't think you can do that anyway AFAIK it uses git .. its only R* that doesn't
not 100% sure since I've not looked for a while 13:32
Zoffix stmuk: you can usually make an NQP package off NQP release and make Rakudo package off a rakudo release but 2017.04.3 uses an unreleased NQP version
stmuk yes this is true 13:33
Zoffix omg...
2017.04.4.... 13:34
timotimo we're learning so much this month!
dogbert17 such action 13:36
Zoffix The largest point release before was .2 13:39
stmuk I sort of wish things were a bit simplier 13:40
Zoffix Normally they are.
You switch the bot off safemode, tell it to release, and ~40m later release is done.
stmuk if you shipped a 2017.04-24-g87501f7b.tar.gz you could probably avoid bumping rakudo 13:41
a bit ugly looking 13:42
Zoffix + that'll also need tweaking download page to recognize such releases + we'll have a release without a tag 13:43
Re-releasing is simpler
ummm
samcv: timotimo but... the regex fix. It was in moarvm wasn't it?
So it's kinda pointless to re-release anything without a point moarvm release. 13:44
stmuk it doesn't break the https download page :) but yes re-releasing is probably safer
Zoffix NeuralAnomaly: status 13:45
NeuralAnomaly Zoffix, [āœ˜] Next release will be in 3 weeks and 6 days. Since last release, there are 7 new still-open tickets (5 unreviewed and 0 blockers) and 54 unreviewed commits. See perl6.fail/release/stats for details
Zoffix At least things will auto-resolve in 3 weeks and 6 days :} 13:46
stmuk: does Rakudo Star need a released nqp? 13:51
Looking at El_Che's packages, looks like they include moarvm + nqp. 13:53
stmuk the process which automatically builds the final tarball has to ftp the 3 tar balls but I could probably stick in a different tar ball quite easily
Zoffix Then maybe best do that. Instead of re-releasing moarvm + nqp + yet another point release of rakudo :o 13:55
or wait until 2017.05 13:56
Zoffix headdesks
stmuk how important is the moarvm fix?
Zoffix c: 2017.04 say 'abcdefgz' ~~ m:i/az/ 13:58
committable6 Zoffix, Ā¦2017.04: Ā«FalseĀ»
Zoffix c: 2017.04 say 'abcdefz' ~~ m:i/za/
committable6 Zoffix, Ā¦2017.04: Ā«ļ½¢zļ½£Ā»
Zoffix stmuk: ^ it fixes that
c: 2017.04 say 'abcdefz' ~~ m:i/zafsdfsdfsdfsdfsdfsdfdsfsdfsdfsdfdsfsdfsdfdsfsdf/ 13:59
committable6 Zoffix, Ā¦2017.04: Ā«FalseĀ»
Zoffix c: 2017.04 say 'abcdefz' ~~ m:i/zafsdfsdfsdfsdfsdfsdfdsfsdfsdfsdfdsfsdfsdfdsfsdfa/
committable6 Zoffix, Ā¦2017.04: Ā«FalseĀ»
stmuk I'll experiment with this shortly 14:00
which moarvm hash should I use?
Zoffix stmuk: current, HEAD, I believe. f0db882 14:01
stmuk is El_Che nxadm I forget> 14:03
Zoffix probably
dogbert17 so how the heck do you build nqp in a proper manner 'perl Configure.pl --backends=moar --prefix=/home/dogbert/repos/rakudo/install/' followed by 'make', 'make test' and 'make install' doesnt do the trick. What am I missing? 14:07
Zoffix --gen-moar 14:08
dogbert17 I'm using the same prefix as when I'm configuring moar
Zoffix: will try 'perl Configure.pl --backends=moar --gen-moar --prefix=/home/dogbert/repos/rakudo/install/' ? 14:09
nope, 'Unhandled exception: Missing or wrong version of dependency '/home/dogbert/repos/rakudo/install/bin/../share/nqp/lib/MAST/Nodes.nqp' (from 'src/Perl6/Pod.nqp')' 14:12
Zoffix dogbert17: you don't need --gen-more if you're building it yourself and that error sounds like you're running `nqp` instead of `./nqp` 14:22
AlexDaniel ā€œThe largest point release before was .2ā€ what was it? 14:23
not after Christmas
ah I see, 2015.07.2
dogbert17 Zoffix: I tried without now. Do you have to rebuild rakudo afterwards? 14:29
Zoffix dogbert17: yes 14:30
dogbert17 thx, that explains it 14:31
timotimo: the change we talked about seems to be working now :) 14:43
stmuk I guess 2015.07.2 was GLR related? 15:45
nine stmuk: no, GLR was merged in September 2015 16:16
Geth nqp/master: 9 commits pushed by (Pawel Murias)++ 16:18
stmuk ah 16:23
Zoffix New blog post: "The Failure Point of a Release": perl6.party/post/The-Failure-Point-of-a-Release 16:43
Geth rakudo/nom: 1bce2e5472 | (Zoffix Znet)++ (committed using GitHub Web editor) | docs/release_guide.pod
Log all 2017.04 point releases
 16:45
nine jnthn: is "muchly" really a word? :)
timotimo it's acceptably a neologism 16:46
TimToady it's neologismly 16:47
pmurias m: use nqp;say(nqp::getobjsc(nqp::hash()));say('lived') 16:49
camelia (signal SEGV)
pmurias m: use nqp;say(nqp::isnull(nqp::getobjsc(nqp::hash())));say('lived') 16:50
camelia 1
lived
pmurias lizmat: is the BEGIN nqp::hash a big performance gain? 16:52
lizmat: the problem with that is that nqp::hashes are usually special cased during serialization but a BEGIN nqp::hash serializes them like a regular object 17:05
Geth star: a0b4754ec7 | (Steve Mynott)++ | tools/star/Makefile
versions of nqp/MoarVM for 2017.04.3
 17:15
star: ef0ccebbda | (Steve Mynott)++ | 3 files
test-mock now needs oo-monitors
 17:20
lizmat pmurias: well, you probably know more about that than I 17:33
when I last checked, the nqp::hash was *not* HLLized 17:34
if that's what you're referring to
afk again& 17:36
Geth star: a7e7b6b92b | (Steve Mynott)++ | 16 files
Bump versions of submodules which at least install fine on Linux
 17:54
samcv Zoffix, good per6.party post 18:02
timotimo Zoffix: a typo in your post: you wrote "create directories / and /bar." but it should read / and /foo instead 18:05
but the rest of the post is good
Zoffix Fixed. Thanks.
samcv ok so we're not having another point release? or we are? or we had one for rakudo but not nqp and moar? so 18:06
timotimo we can put non-release moarvm and nqp into the rakudo star
Geth star: cdbe6e45b3 | (Steve Mynott)++ | docs/announce/2017.04.md
import announce
 18:13
pmurias Zoffix: re Perl6 VIP, it seems a good idea. 18:21
stmuk pl6anet.org/drop/rakudo-star-2017.04-RC0.tar.gz 18:42
MasterDuke_ aren't there some utility functions somewhere to test the output of stderr? 18:55
moritz yes 18:57
t/spec/packages/Test/Util.pm
MasterDuke_ thanks
Zoffix MasterDuke_: is_run in particular 19:00
MasterDuke_ also thanks 19:01
timotimo hm 19:02
long ago i think we used to upload release tarballs before announcing them and only posted the announcement and uploaded to the "official place" when people have given a thumbs-up 19:03
Zoffix what "people"?
MasterDuke_ does anyone have an opinion about whether tests for RT #113954 should go in roast or rakudo's tests? 19:05
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=113954
Zoffix would put in rakudo
MasterDuke_ was leaning there myself. but do those tests have access to is_run? 19:07
Zoffix nope 19:08
MasterDuke_ any reason not to copy it over? 19:09
Zoffix nope
timotimo Zoffix: well, more than just one person 19:14
no matter who in particular. just get reports from a few people that things work out fine 19:15
MasterDuke_ isn't there some thought of lib/Test.pm6 going away? if not, should i just copy t/spec/packages/Test/Util.pm to lib/Test/Util.pm6? or just copy the functionality i need directly into the .t file? 19:16
Zoffix What do you do with the tag then tho? You can't move it even if people find some issues
MasterDuke_: no such thought
timotimo you can forcepush over a tag 19:17
Zoffix MasterDuke_: and don't add it to lib add it somewhere in t/
timotimo hm. does the tag need to exist in order for a release tarball to be attempted? 19:18
maybe i'm thinking of star the whole time!?
MasterDuke_ t/lib? t/packages? anyone care? 19:19
got err: "Usage:\n getout-2074-60417.code 'foo bar' \n" 20:03
expected err: "Usage:\n -e '...' 'foo bar'"
timotimo that's fun. 20:07
Zoffix Yeah, it creates files it runs then 20:08
Just use `like` and read from `run` instead of using is_run
is run(:err, $*EXECUTABLE, <some arts>).err.slurp(:close), 'somethinng or other'
*args 20:09
MasterDuke_ is_run is broken?
Zoffix .
MasterDuke_ `is_run('multi MAIN(q|foo bar|) {}', 'foo bar', { err => "Usage:\n -e '...' 'foo bar' \n" }, 'description'` is what i ran 20:10
Zoffix MasterDuke_: what's `'foo bar'`? 20:11
MasterDuke_ a string with a space in it 20:12
Zoffix ...
MasterDuke_ i'm testing that foo bar doesn't work and suggests 'foo bar' 20:13
Zoffix You're sending it to STDIN tho 20:14
MasterDuke_ yeah, and then it doesn't hit the multi and the usage goes to stderr 20:15
Zoffix Then why send it at all? 20:16
It'll still have the getout* part because is_run uses a file
MasterDuke_ to match the use case in the RT 20:17
but, true, it's not necessary
Zoffix That's not the usecase in the ticket. In the ticket you're passing as args, not STDIN
There are docs for is_run: github.com/perl6/roast/blob/master...#L305-L351 20:18
MasterDuke_ oh, right, STDIN 20:19
`is_run('multi MAIN(q|foo bar|) {}', :args['foo', 'bar'], { err => "Usage:\n -e '...' 'foo bar' \n" }, 'description'` still has the getout... in the 'got err' 20:23
so i'm ending up with `is run(:err, $*EXECUTABLE, ['-e', 'multi MAIN(q|foo bar|) {}', 'foo', 'bar']).err.slurp, ...` 20:52
fwiw, slurp(:close) would cause `The spawned command '<...>' exited unsuccessfully (exit code: 2)`
Geth rakudo: MasterDuke17++ created pull request #1066:
Add tests for RT #113954		 21:11
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=113954
Geth rakudo: MasterDuke17++ created pull request #1067:
Add missing '.' to end of expected text		 21:14
MasterDuke_ m: role R { method r {...} }; class C is R { method r { say "hi" } } # RT #118263 21:48
camelia 5===SORRY!5=== Error while compiling <tmp>
Method 'r' must be implemented by R because it is required by roles: R.
at <tmp>:1
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=118263
timotimo you want "does" not "is" there 21:50
MasterDuke_ you can "is" roles though
timotimo yeah
it'll stub the role so the class can derive from it
MasterDuke_ m: role R { method r { say "hi" } }; class C is R { }; C.new.r
camelia hi
timotimo but it'll give you a stranger error message, still
MasterDuke_ i feel like the error message would end up a paragraph 21:52
timotimo haha 21:54
MasterDuke_ Method 'r' must be implemented by R because it is required by roles: R. Classes can't implement methods stubbed in roles when they "is" the role, did you mean to "does" the role?
timotimo "can't pun a role with required methods"
MasterDuke_ timotimo: that's pretty good 21:58
timotimo if it could also figure out that the pun was made because of a "is" instead of "does", that'd be better 21:59
MasterDuke_ the backtrace starts in `sub trait_mod:<is>`, so hopefully should be possible 22:00
is there a way to tell if the $parent in `sub trait_mod:<is>(Mu:U $child, Mu:U $parent)` has required methods? 22:04
samcv can people here weigh in on these non-standardized tags in META gist.githubusercontent.com/samcv/b...f60af8fe/-
some are wrong, and some maybe should be added to the spec. but what do you guys think 22:05
timotimo i didn't even see that i had already answered that bug! 22:19
that bug is *old*
oh 22:20
i was also the one who created that bug
MasterDuke_ heh, yeah. was just looking through old bugs to see if there was anything easy to pick off 22:21
P6opaque: must compose Whatever before allocating 22:28
don't think i've seen that before
timotimo it's when you try do put a * very early into the core setting
MasterDuke_ ah, thanks. should be easy to work around 22:29
m: role R { method a {...}; method b { say "bee" }; method c {...} }; class C is R { }; C.new 22:38
camelia 5===SORRY!5=== Error while compiling <tmp>
Method 'a' must be implemented by R because it is required by roles: R.
at <tmp>:1
MasterDuke_ locally that says `Can't pun role R with required methods: a, c`
timotimo: think that ^^^ looks ok? 22:39
timotimo that makes it sound like you're "punning a role with methods"
like, you're using methods to pun something
i'd phrase it more like "role R because it has required methods: ..." 22:40
MasterDuke_ yeah, that's better 22:42
timotimo i think i'll be going to bed soon 22:43
MasterDuke_ "Class C can't pun role R because it has required methods: a, c" 22:46
how's that?
timotimo do you actually find out that it's Class C that's doing it? 22:47
MasterDuke_ well, i find out the C part
timotimo yeah, that sounds good
MasterDuke_ can anything else "is" things?
timotimo can we find a phrasint that'd somehow hint at "maybe you wanted to use 'does' instead?"
everything can is things :P 22:48
trait_mod:<is> has many candidates
m: say &trait_mod:<is>.^candidates
camelia No such method 'candidates' for invocant of type 'Perl6::Metamodel::ClassHOW'
in block <unit> at <tmp> line 1
timotimo m: say &trait_mod:<is>.candidates
camelia (sub trait_mod:<is> (Mu:U $child, Mu:U $parent) { #`(Sub|31809120) ... } sub trait_mod:<is> (Mu:U $child, :$DEPRECATED!) { #`(Sub|31816264) ... } sub trait_mod:<is> (Mu:U $type, :$rw!) { #`(Sub|31816416) ... } sub trait_mod:<is> (Mu:U $type, :$nativesizeā€¦
timotimo c: HEAD .say for &trait_mod:<is>.candidates 22:49
committable6 timotimo, gist.github.com/180c435a12693e68cc...df29d97237
MasterDuke_ ah, but on the one does `^add_parent` 22:50
*only
timotimo yeah, only the Mu:U, Mu:U one, i bet 22:51
set a dynamic variable $*PUNSTER :D :D :D
MasterDuke_ dinner &. will PR after 22:52
timotimo cool. i'm going to bed soon 22:53
MasterDuke_ later... 22:54

Powered by Cro and the RakuĀ® Programming Language.

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

Thank you!