rformance of internals [ed4ef3b][f85978b]
The following people contributed to this release:
Zoffix Znet, Elizabeth Mattijsen, Samantha McVey, Pawel Murias,
Will "Coke" Coleda, Jonathan Worthington, Wenzel P. P. Peppmeyer,
Antonio Quinonez, Altai-man, Cale, Daniel Green, Tom Browder, Mori
0][5843ee6][7c279c3][318f8ee][4ef1e69][9d497e9]
[b597398][4bc826d][9da50e3][2a2e460][0633f03][d444f65][f94a2c7]
The following people contributed to this release:
Zoffix Znet, Elizabeth Mattijsen, Wenzel P. P. Peppmeyer, Samantha McVey,
Will "Coke" Coleda, Pawel Murias, Jonathan Worthing
62][b64f210][1277fb5]
[463898a][3f36508][65037c3][e408e47][6ef7b59][a4b30dc][7875eaf][d793e21][bf63719][9a2446c]
[0dbe451][1867099][2694f5d]
The following people contributed to this release:
Zoffix Znet, Elizabeth Mattijsen, Pawel Murias, Larry Wall, Samantha McVey,
Timo Paulssen, Jona
h.resolve fix for JVM, as it does not yet know
how to do utf8-c8 decode [88a6facc]
The following people contributed to this release:
Larry Wall, Zoffix Znet
If you would like to contribute or find out more information, visit
<http://perl6.org>, <http://rakudo.org/how-to-help>,
[f4f1c42]
The following people contributed to this release:
Stefan Seifert, Zoffix Znet
If you would like to contribute or find out more information, visit
<http://perl6.org>, <http://rakudo.org/how-to-help>, ask on the
mailing list, or ask on IRC #perl6 on freenode.
Additionally,
ues with false positive case-insensitive regex matches
when only start of string and end of string match
[f756b4b54f][25048824c8]
The following people contributed to this release:
Samantha McVey, Timo Paulssen, Larry Wall, Zoffix Znet
If you would like to contribute or find out more informat
391b][b1fbd133][7404c706][762fd239]
[fec547a1][5ec8a464][8088f080][45305eca][e7087f29][f4017c32][3f7d1334][6ea2f12e]
[788e6de6][3fb3c27e][09506dc8]
The following people contributed to this release:
Zoffix Znet, Elizabeth Mattijsen, Pawel Murias, Daniel Green, Samantha McVey,
Stefan Seif
Julián Merelo Guervós, Gabor Szabo, Trey Harris, Eckhart Arnold,
Julien Simonet, Moritz Lenz, Timo Paulssen, flussence, raiph, Kris Shannon,
Aleks-Daniel Jakimenko-Aleksejev, Fyodor Sizov, Zoffix Znet
If you would like to contribute or find out more information, visit
<http://perl6.org>, <
eptions are caught [1a4d9493]
+ Assorted internal improvements to CPU/memory use
[3d2a521c][5a80412c][c4e14731][19be8722]
[f03a176c][fff43337][f71cbed4][79ce1a99][640404fc][b4561229][30619e8d][9d14a724][a2a0d5c6]
[66aef589][a95c70bd][d7e10466][73c3bcc6][7f109ed7][80b3e89b][0
Quoting Darren Duncan :
On 2017-07-24 11:40 AM, Steve Mynott wrote:
A useful and usable production distribution of Perl 6
The download links on http://rakudo.org/how-to-get-rakudo/ still
name the April release and will need updating. -- Darren Duncan
I updated the link text now (the link
Quoting R0b0t1 :
Are there any releases signed by the developers? The official releases
located at https://rakudo.perl6.org/downloads/star/ do not seem to
have signatures available.
There's Rakudo the compiler and Rakudo Star distribution
which is the compiler + docs + some modules.
Yes, the
Quoting Parrot Raiser <1parr...@gmail.com>:
Round trips to the OS, like repeated "says", have been slow relative
to internal processes since the dawn of time.
In this case, there are no trips. It's the *parsing* time that's slow.
In fact, if you change it to `$ = ‘a’;` it's equally slow.
If you track latest rakudo changes by means of a local checkout of the
development repository, please take notice that we renamed our
unusually-named main development branch from nom to the more
traditional name master
See
http://rakudo.org/2017/10/27/main-development-branch-renamed-fro
On 2017-12-11 12:22 PM, Sean McAfee wrote:
Well, not really. I don't think x %% 0 should return a Failure at all.
Is there a particular problem the current implementation fails to
solve? In boolean
context `x %% 0` *is* equivalent to False. The Failure carries
additional information
to th
I was going to suggest that your zef may be too old and doesn't yet
know how to
handle the "+" in the dependency version. However, I don't see any
module in the
ecosystem use the `0.0.7+` as version requirement any more (I know we had
one in the past, but I'm now unsure whether zef was taug
Tadeusz “tadzik” Sośnierz, thebooort, Thor Michael Støre,
threadless-screw, thundergnat, Tim Smith, Timo Paulssen, Tobias Boege,
Tobias Leich, Tom Browder, tomboy64, Tommy Stanton, Trey Harris,
Tzu-Li "tison" Chen, Valentin Anger, ven, Viacheslav Lotsmanov,
vinc17fr, Vladimir Marek, Vynce Mo
ijsen, Jonathan Worthington, Jan-Olof Hendig, Zoffix Znet,
Josh Soref, Pawel Murias, Wenzel P. P. Peppmeyer, Aleks-Daniel
Jakimenko-Aleksejev,
Tom Browder, Daniel Green, Jonathan Stowe, titsuki, Stefan Seifert,
Pepe Schwarz,
Christian Bartolomäus, Will "Coke" Coleda, Steve Mynott, T
1 on attempting to much around
with '/'
Cheers,
ZZ
Quoting Brandon Allbery :
On Mon, Jul 4, 2016 at 6:44 PM, Zoffix Znet via RT <
perl6-bugs-follo...@perl.org> wrote:
> Ticket should be closable once a test has been added to Roast.
Is it really appropriate to attempt to cr
ug in panda. It wasn't a
pretty picture.
It's fine to check failure modes on an existing directory we create
during testing, but I'm a definite -1 on attempting to much around
with '/'
Cheers,
ZZ
Quoting Brandon Allbery :
On Mon, Jul 4, 2016 at 6:44 P
🎺🎺🎺 REMINDER: the next version of Rakudo will be released this Saturday.
You are invited to update the ChangeLog, the ROADMAP, or any other
relevant source of information. You are also invited to run the full
stresstest on your machine, to ensure the release is tested on as many
architectur
ly some of the changes in this release. For a more
detailed list, see “docs/ChangeLog”.
The following people contributed to this release:
Elizabeth Mattijsen, Zoffix Znet, Jan-Olof Hendig, Stefan Seifert, Tom
Browder, Wenzel P. P. Peppmeyer, Pepe Schwarz, Brock Wilcox, Jonathan
Worthington, Ale
Quoting Parrot Raiser <1parr...@gmail.com>:
When's the next Rakudo* likely to be out?
There's a serious consideration to cut a release this month, so you
will likely see one in the next couple of weeks.
Cheers,
ZZ
en incorrect arguments
+ Improved error message when .polymod is given a zero as divisor
+ Efficiency:
+ Str.samecase is now 5x faster
+ Str.indices is 10% faster
+ Str.rindex is 30% faster
+ Str.index is 30% faster
The following people contributed to this release:
Zoffix Znet, Ste
Perhaps, we should evaluate some of the leap-second estimation
algorithms. There are
more leap second problems in Rakudo besides the .from-posix, that I
now opened in
https://rt.perl.org/Ticket/Display.html?id=128752
Quoting Zefram :
Zoffix Znet via RT wrote:
Returning zero is much
geLog”.
The following people contributed to this release:
Zoffix Znet, Wenzel P. P. Peppmeyer, Elizabeth Mattijsen, Pawel Murias,
Jonathan Worthington, Altai-man, Larry Wall, Tom Browder, Will "Coke" Coleda,
Jan-Olof Hendig, Stefan Seifert, Moritz Lenz, Itsuki Toyota,
Christopher Botto
# Announce: Rakudo Perl 6 compiler, Release 2016.08.1
On behalf of the Rakudo development team, I'm announcing an
out-of-schedule release of the Rakudo Perl 6 compiler.
Rakudo is an implementation of Perl 6 on the Moar Virtual Machine[^1].
This release is a point release in addition to the regu
de is not affected by
this change.
The following people contributed to this release:
Zoffix Znet, Elizabeth Mattijsen, Jonathan Worthington, Daniel Green,
Tom Browder, Jan-Olof Hendig, Will "Coke" Coleda, Stefan Seifert, LemonBoy,
Pawel Murias, Timo Paulssen, Itsuki Toyota, Christia
rformance
+ Made dir() about 20% faster
+ Made Regex.Bool about 2x as fast
+ Made Str.match about 3% faster
The following people contributed to this release:
Zoffix Znet, Pawel Murias, Elizabeth Mattijsen, Wenzel P. P. Peppmeyer,
Jonathan Worthington, Will "Coke" Coleda, Pepe Schw
now about 40% faster [b5aa3c5]
+ Rational.base is now about 30% faster [b5aa3c5]
+ Various streamlining of code that's hard to measure the final impact of
The following people contributed to this release:
Elizabeth Mattijsen, Zoffix Znet, Will "Coke" Coleda, Pawel Murias,
[474ea33]
+ Made print, say and note 25% faster to stderr and stdout [e9ce28a]
The following people contributed to this release:
Zoffix Znet, Pawel Murias, Elizabeth Mattijsen, Wenzel P. P. Peppmeyer,
Will "Coke" Coleda, Samantha McVey, Altai-man, Jonathan Worthington,
Stefan Seife
+ Made reified List.Array about 3x faster [c9a9bc8]
+ Made List/Array.sum about 30% faster [017c6cf]
+ Made List/Array.fmt with no args about 60x faster [22e589a]
+ Made List/Array.fmt("%s") about 60x faster [7ef3682]
+ Made List/Array.join about 20% faster [ed482ec]
The fol
All of the Range ~~ Range stuff is now fixed in
https://github.com/rakudo/rakudo/commit/8477f3b6b0
and tested in
https://github.com/perl6/roast/commit/e152a0ff3a37ef56c4c68af09421b47d5ad9d93c
https://github.com/perl6/roast/commit/3688301754e46a8b3afdbfad4e73c377e592e339
https://github.com/perl6/r
On Sat, 03 Sep 2016 21:03:12 -0700, c...@zoffix.com wrote:
> To add, the cause is .is-lazy on slurpy args seems to attempt to reify
> the entire sequence:
>
> -> *@a { @a.is-lazy.say }(1…∞) # hangs
The rotor hang fixed in https://github.com/rakudo/rakudo/commit/d7b82149d31da0
The slurpy hang fix
On Tue, 27 Dec 2016 11:02:17 -0800, c...@zoffix.com wrote:
> In this code, I would've expected the second multi to be used, since
> I'm not providing
> any named args. I'm fuzzy on whether named params affect multi
> dispatch, but even if they
> wouldn't the multi without any named params is later
On Thu, 09 Feb 2017 16:51:00 -0800, samant...@posteo.net wrote:
> > 1.1.base(1)
> Attempt to divide 2.30258509299405 by zero using /
> in block at line 1
>
> Fudged roast test in S32-num/base.t
Thank you for the report. This is now fixed.
Fix: https://github.com/rakudo/rakudo/commit/301bcf93
On Mon, 06 Feb 2017 04:04:16 -0800, consult...@jnthn.net wrote:
> Discovered this after some $dayjob code got busted by updating Rakudo.
> After bisecting, I got it down to this commit:
>
> https://github.com/rakudo/rakudo/commit/fd8df7f2ad509689a64b8825e1c4bb622cf7486f
>
> And from that thankful
On Sat, 09 Jan 2016 05:05:06 -0800, lucasbuchala wrote:
> An itemized empty list is getting ".perl"-stringified as "$()", which
> I think is wrong since $() means some idiom using "$/". The fix should
> be just to make it stringify as "$( )" (with a space in the middle) or
> maybe "().item" for cla
Golfed a bit:
m: { foo => class {} }()
rakudo-moar 266f34: OUTPUT«When invoking 1 '', provided outer frame
0x322f4e0 (3 '') does not match expected static frame 0x322f5e8 (2 '')
in block at line 1»
The avoidance of reduction is for optimization purposes.
The .norm stuff is fixed now in
https://github.com/rakudo/rakudo/commit/aac9efcbda and tested in
https://github.com/perl6/roast/commit/7d0daf5286
However, there's a data-race in Rational.REDUCE-ME and it needs to go:
https://irclog.perlg
On Sat, 28 Jan 2017 16:42:46 -0800, mt1...@gmail.com wrote:
> Hi,
>
> I get the following error using version 2016.08.1-66-g1ff1aae built on
> MoarVM version 2016.08
> implementing Perl 6.c.
>
> Cannot resolve caller BUILD(CC+{RR}: ); none of these signatures match:
> (CC $: Str :$t!, *%_)
I found where the LEAVE was mentioned and removed it.
The .close you're calling is actually from IO::Pipe, not IO::Handle.
Probably something else should be clarified in the docs to avoid that sort of
confusion as well.
Marked it as TODO for my IO grant thing and will resolve this ticket as pa
On Mon, 13 Feb 2017 14:38:03 -0800, na...@cpan.org wrote:
> $ echo %windir%
> C:\WINDOWS
>
> $ echo %WINDIR%
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> (Any)
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -v
> This is Raku
On Mon, 13 Feb 2017 14:38:03 -0800, na...@cpan.org wrote:
> $ echo %windir%
> C:\WINDOWS
>
> $ echo %WINDIR%
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> (Any)
>
> $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV"
> C:\WINDOWS
>
> $ c:\opt\perl6-mingw\bin\perl6 -v
> This is Raku
On Sat, 11 Feb 2017 03:29:18 -0800, moritz wrote:
> sub f($x) {
> sub {
> if True {
> say &?ROUTINE.name
> }
> }
> }.(42)()
>
> This prints f on Rakudo 2017.01-170-gc0a907f built on MoarVM version
> 2017.01-31-g20dfa6b
>
> &?ROUTINE sh
On Mon, 13 Feb 2017 21:04:37 -0800, raiph wrote:
> This comment is technically redundant. And maybe not helpful. I
> apologize if it's annoying to anyone.
Not annoying, but I feel we all have thoroughly confused bdfoy by now :P
Some minor corrections:
> 4.1 `sink some.expression;`
>
> In stark
Just realized something: I fixed Str ~~ Numeric to not throw, so on HEAD there
won't be any Failures at all with the sample code.
I tried changing the tests to use $a + $b instead of $a ~~ $b, but then the
DESTROY warning does not occur...
... should this ticket be closed?
On Thu, 18 Feb 2016 09:51:34 -0800, ug...@cpan.org wrote:
> The assignment fix can be simplified further:
> $ perl6 -e 'my $p = shell("false", :out); |$p.out.close; say
> $p.exitcode'
> 1
Or even simpler:
$ perl6 -e 'my $p = shell("false", :out); $p.out.close.exitcode.say'
1
.close doesn
Looks like several other tests in S17-procasync/basic.t would be failing as
well if it weren't for the explicit kludges[^1][^2] added to replace "\r\n" to
"\n". And `grep -nFR '\r\n' | grep subs` shows[^3] 32 potential places with a
similar workaround.
Pretty LTA for portable Perl 6 code to req
Thank you for the report. This is now fixed:
Rakudo fix:
https://github.com/rakudo/rakudo/commit/dc69dafc42
https://github.com/rakudo/rakudo/commit/11d005e605
https://github.com/rakudo/rakudo/commit/4b85db6e8c
Tests:
https://github.com/perl6/roast/commit/a460cdc7ac
https://github.com/perl6/roast/
On Sun, 01 May 2016 04:12:34 -0700, alex.jakime...@gmail.com wrote:
> This bug report is somewhat related to
> https://rt.perl.org/Ticket/Display.html?id=128046
>
> get() crashes with a weird error if the stream has ended.
>
> Command:
> perl6 -ne 'get' <<< $'hello\nworld\ntest'
>
> Result:
> wo
On Tue, 21 Feb 2017 05:15:56 -0800, jar...@bansu.fi wrote:
> EXAMPLE:
> my %hash = foo => 1;
> if %hash:exists {
> say "not gonna print this";
> }
> my $key = 'b';
> if %hash«$key»:exists {
> say "why i'm here";
> }
>
> OUTPUT:
> why i'm here
>
> EXPECTED RESULT:
> (Should not print anything)
>
On Wed, 22 Feb 2017 19:32:31 -0800, comdog wrote:
> Here's a curious change over in precision:
>
> > 4.999 ~~ 0..^5
> True
> > 4. ~~ 0..^5
> False
>
> I figure this is an implementation detail that ties to storage, but
> one of the selling points of Per
On Thu, 23 Feb 2017 22:01:25 -0800, j...@durchholz.org wrote:
> Somewhat offtopic:
Feels like a bad place for offtopic discussions. You can ask questions in the
same IRC channel you evaled your example.
> toolforger: p6: say Inf cmp Inf
> camelia: rakudo-moar 320c2f: OUTPUT: «Same»
>
> I.e. In
On Fri, 24 Feb 2017 08:21:12 -0800, c...@zoffix.com wrote:
> Originally encountered this grepping CORE:: symbols and calling
> .unique on the result.
>
> Golfed it down to nqp::p6recont_ro(Scalar):
>
> m: unique Scalar
> rakudo-moar d41b68: OUTPUT: «(signal SEGV)»
>
> m: use nqp; nqp::p6recon
On Mon, 27 Feb 2017 00:21:17 -0800, zef...@fysh.org wrote:
> > say "a"; "a" + 2; say "b"
> a
> > "a" + 2
> Cannot convert string to number: base-10 number must begin with valid
> digits or '.' in '^a' (indicated by ^)
> in block at line 1
>
> In both of these cases the addition signals an exce
On Mon, 27 Feb 2017 14:27:04 -0800, zef...@fysh.org wrote:
> Zoffix Znet via RT wrote:
> >Fix: https://github.com/rakudo/rakudo/commit/db70a1fda8
>
> This doesn't distinguish between an exception being thrown and the
> expression evaluating to an exception object.
On Mon, 27 Feb 2017 14:35:17 -0800, zef...@fysh.org wrote:
> > try { my Int $a; $a = "foo" }; say ?$!.backtrace; say
> > ?$!.perl.EVAL.backtrace
> True
> False
>
> .perl.EVAL is failing to round-trip the exception object, as
> demonstrated
> by the differing truthiness of the value returned by .ba
On Mon, 27 Feb 2017 16:53:02 -0800, zef...@fysh.org wrote:
> Zoffix Znet via RT wrote:
> >Fix: https://github.com/rakudo/rakudo/commit/61a65cee3d
>
> You've just moved the problem along. There's now a new class of
> object that, if evaluated to, will be treate
Thank you for the report. This is now fixed.
Fix: https://github.com/rakudo/rakudo/commit/76f71878da
Test: https://github.com/perl6/roast/commit/908348eef1
On Mon, 27 Feb 2017 01:59:07 -0800, elizabeth wrote:
> Fixed with https://github.com/rakudo/rakudo/commit/a274bdd122 , tests
> needed
Test added: https://github.com/rakudo/rakudo/commit/0f37dd38e0
I went to write a test for this, but can't repoduce the issue. I tried a
handful of releases with the IRC bot, then built 2016.01 release and the
mentioned 86a90be commit, but none of them fail.
Perhaps this is an OSX-only issue? Could someone with OSX try reproing it on
86a90be commit and if t
Hi, would you please include the version you're using?. You can get it by
running `perl6 -v`
Sorry, wrong example of failure mode. It seems to happen in `while`:
m: while $++ < 5 { when {True} {Failure.new} }
rakudo-moar 9d497e: ( no output )
FWIW, this bug makes at least mild exploitation possible, depending on how the
program validates input:
Setup: dir and input check to ensure user-supplied path is not outside of it:
13:41 IOninja m: "/tmp/root/tmp".IO.mkdir;
"/tmp/root/secret.txt".IO.spurt: 'p4sswrd';
13:41
On Sat, 25 Feb 2017 22:06:29 -0800, cookbook_...@yahoo.co.jp wrote:
> See the following example:
>
> $ perl6 -e 'my @a; @a = [[1, 2], [3, 4]]; @a[0;*].say;'
> (1 2)
>
> $ perl6 -e 'my @a[2;2]; @a = [[1, 2], [3, 4]]; @a[0;*].say;'
> Partially dimensioned views of arrays not yet implemented. Sorry
On Sat, 25 Feb 2017 22:06:29 -0800, cookbook_...@yahoo.co.jp wrote:
> See the following example:
>
> $ perl6 -e 'my @a; @a = [[1, 2], [3, 4]]; @a[0;*].say;'
> (1 2)
>
> $ perl6 -e 'my @a[2;2]; @a = [[1, 2], [3, 4]]; @a[0;*].say;'
> Partially dimensioned views of arrays not yet implemented. Sorry
7;". My best guess is that because it first tries to figure
> out which candidate to invoke and then actually calls into the candidate
> (which starts with code generated by the fast binder) it hits a bind
> failure as if you had directly invoked that candidate yourself but with
>
On Sat, 04 Mar 2017 13:24:08 -0800, comdog wrote:
> This is the example from the Tap docs. I expect the output to be
> "Tap closed", but I get no output using 2017.01:
>
> my $s = Supplier.new;
> my $tap = $s.Supply.tap(
> -> $v { say "the value is $v" },
> done=> { say
Related: https://rt.perl.org/Ticket/Display.html?id=128977#ticket-history
Ooops. Never mind. That hang is due to RT#130940
As for this ticket, I've added fudged tests to cover it now:
https://github.com/perl6/roast/commit/2fa32e11eb
Please note, this ticket is now marked as a release blocker, with the release
scheduled to occur on March 18, 2017.
On Wed, 08 Mar 2017 04:46:55 -0800, blackcatoverw...@gmail.com wrote:
> Split a null string with skip-empty not working.
>
> Code:
>
> say "".split(';', :skip-empty).perl;
>
> say "".split(';').perl;
>
> Result:
>
> ("",)
>
> ("",)
>
> perl6 -v :
>
> This is Rakudo version 2017.02 built on
On Tue, 28 Feb 2017 14:41:07 -0800, sml...@gmail.com wrote:
> my &a = *+1;
> my &b = */2;
>
> say &a.arity; # 1
> say &b.arity; # 1
> say (&a o &b).arity; # 0
>
> say &a.count; # 1
> say &b.count; # 1
> say (&a o &b).count; # Inf
>
On Thu, 09 Mar 2017 04:06:27 -0800, zef...@fysh.org wrote:
> > my @a is default(Nil); @a[0] = Nil
> Nil
> > @a[0]
> Nil
> > @a.perl.EVAL[0]
> (Any)
>
> .perl.EVAL fails to round-trip the Nil element value in the Array.
> Nil itself round-trips fine, so the failure here is specific to the Array.
>
On Tue, 28 Feb 2017 14:41:07 -0800, sml...@gmail.com wrote:
> my &a = *+1;
> my &b = */2;
>
> say &a.arity; # 1
> say &b.arity; # 1
> say (&a o &b).arity; # 0
>
> say &a.count; # 1
> say &b.count; # 1
> say (&a o &b).count; # Inf
>
On Fri, 10 Mar 2017 19:11:53 -0800, ddgr...@gmail.com wrote:
> [21:51] m: use CheckSystemDependency ( $name ) { say "lol" }
> [21:51] <+camelia> rakudo-moar f190f2: OUTPUT: «===SORRY!===Cannot call
> method 'List' on a null object»
> [21:51] that's meant to be "sub" instead of use
Golfed a bi
Rakudo:
PR that added support: https://github.com/rakudo/rakudo/pull/1029/
Revert commit: https://github.com/rakudo/rakudo/commit/9644fc360f
Roast:
PR that added tests: https://github.com/perl6/roast/pull/246
Revert commit: https://github.com/perl6/roast/commit/b4d4df1e09
Docs:
Issues on new tern
Per discussion[^1], closing this RFC due to current lack of interest in the
feature.
[1] https://irclog.perlgeek.de/perl6/2017-03-15#i_14269321
Another piece-meal fix: for Bool:U.Str:
https://github.com/rakudo/rakudo/commit/3de5fb24c9
https://github.com/perl6/roast/commit/de5f00b909
On Wed, 17 Aug 2016 15:42:04 -0700, zef...@fysh.org wrote:
> > my $a = 3; my $c = \($a); say $c.WHICH; $a = 555; say $c.WHICH
> Capture|(Int|3)
> Capture|(Int|555)
>
> The Capture's identity, as judged by .WHICH, is apparently changing.
> That should never happen. To accurately reflect the object
On Wed, 08 Mar 2017 03:55:38 -0800, sml...@gmail.com wrote:
> my $x = 42;
>
> my $c1 = \($x);
> my $c2 = \(42);
>
> say $c1 eqv $c2; # True
> say $c1 === $c2; # True
> say $c1.WHICH;# Capture|(Int|42)
> say $c2.WHICH;# Capture|(Int|42)
>
> Since the two captures in this example are not
On Mon, 06 Mar 2017 12:51:12 -0800, TimTom wrote:
> If you pass an undefined value into starts-with, it loops forever
> because the Cool class has a wrapper method that casts the parameters
> to Str then invokes that. The Str class, however, defines the method
> as only taking a defined string. So
On Sat, 30 Apr 2016 11:16:44 -0700, barto...@gmx.de wrote:
> Starting with rakudo commit fe2be65806 two tests in S16-io/supply.t
> start to fail with rakudo-j. The following rakudo commit 463e7589a1
> seems to change the code path for the tests in question, but also
> makes them fail. Only if one r
Thank you for the report. However, there's no bug here and I'm going to reject
this ticket.
> Another option is to make it return 5 (kinda DWIM)
No, it's not another option because that doesn't make any sense mathematically.
The math operations lcm[^1] and gcd[^2] ops perform apply to integer
On Sun, 04 Oct 2015 12:57:26 -0700, duelafn wrote:
> http://doc.perl6.org/type/IO::Path#method_absolute
>
> Says: method absolute (IO::Path:D: $base = ~$*CWD --> IO::Path:D)
>
> But IO::Path in Rakudo returns a string.
>
> S16 doesn't really commit to an answer, saying just "absolute the
> abs
On Fri, 30 Dec 2016 14:06:51 -0800, comdog wrote:
> indir is in S16 but not documented elsewhere, but it's a really cool
> feature that I think many people will find useful. It's certainly much
> more convenient
>
> indir '/Users/brian', {
> put "Directory is $*CWD";
> }
>
> indir '/etc',
On Tue, 04 Apr 2017 02:52:53 -0700, comdog wrote:
> I originally asked about this on Stackoverflow
> (http://stackoverflow.com/q/43199427/2766176)
>
> This `try` catches the exception:
>
> try die X::AdHoc;
> say "Got to the end";
>
> The output shows that the program continues:
>
> Got to the
On Sun, 02 Apr 2017 19:19:11 -0700, lloyd.fo...@gmail.com wrote:
> use Grammar::Tracer;
> grammar G {
> token TOP { || }
> token first-fail { '?' }
> token second-succeed { '!' }
> token thing { "foo" }
> }
> note G.parse("foo!")
>
> #grammar tracer output:
>
> TOP
> | first-
I only now realized what this message actually means /o\
A Failure that neither exploded nor was handled got GCed, potentially
indicating an error in user's code due to missed Failures.
I improved the message in https://github.com/rakudo/rakudo/commit/75c3f29100
do version 2017.03-20-g027aa54 built on MoarVM version
> 2017.03-7-g029d121
> implementing Perl 6.c.
>
> The error points to at gen/moar/stage2/NQPHLL.nqp:1099
> (/home/zoffix/.rakudobrew/moar-
> nom/install/share/nqp/lib/NQPHLL.moarvm:EXPR_reduce)
>
> However, I don'
On Thu, 06 Apr 2017 13:46:00 -0700, alex.jakime...@gmail.com wrote:
> Code:
> my @a = ;
> my @b = <1 2 3>;
> my @c = @a, @b;
> say @c
>
> Result:
> [[a b c] [1 2 3]]
>
>
> So with arrays, nothing is flattened and you get an array with two
> elements. Makes sense.
>
> And if we want to get a dif
Hi,
> Should junctions only care about unique values?
No, Junctions aren't about unique values. They're a superposition of values
that threads through routines without them even knowing they're working with a
Junction:
m: my $a = 3|3; my $x++ for ^$a; say $x
rakudo-moar 49c0ab: OUTPUT
On Fri, 07 Apr 2017 10:08:54 -0700, comdog wrote:
> Consider this junction which you probably shouldn't make but you know
> will happen in the hands of users:
>
> any( 5, 'flarg' ) == 5
>
> Despite having an element that satisfies the condition, it blows up
> because one of them doesn't:
>
>
And if you just give a Failure into a Junction it doesn't explode it and
propagates it:
m: say so any("flarg",42)».Numeric
rakudo-moar 15a25d: OUTPUT: «True»
m: say sub ($_) { .^name }( +any("flarg",42) )
rakudo-moar 15a25d: OUTPUT: «any(Failure, Int)»
Wonder if there'
On Fri, 07 Apr 2017 19:09:55 -0700, lloyd.fo...@gmail.com wrote:
> IMO any() junctions should propagate exceptions regardless of whether one of
> its other values succeeded
Well, they do. The exception gets thrown. It just aborts all of the results. In
a superimposition of multiple universes cal
On Thu, 02 Mar 2017 02:29:27 -0800, zef...@fysh.org wrote:
> > spurt("foo\x[0]bar", "wibble")
> True
>
> The above writes to a file named "foo". It is less than awesome that
> Perl 6 accepts "foo\x[0]bar" as a pathname, when it doesn't resemble
> any pathname valid on the OS, and silently treats
On Tue, 16 Aug 2016 18:25:28 -0700, ddgr...@gmail.com wrote:
> Paraphrasing from IRC where my first comment starts here:
> http://irclog.perlgeek.de/perl6/2016-08-17#i_13035789
>
> My feeling has always been that Perl 6's errors are good, but I'm
> sympathetic to whoever it was that complained tha
02 c: 2017.03,HEAD class { has uint $.x }.new: :x(2**64-1)
> 13:02 committable6Zoffix, ¦2017.03: «» ¦HEAD(fbc6697): «Cannot
> unbox 64 bit wide bigint into native integer in block at
> /tmp/EY1TW4ElM7 line 1 «exit code = 1»»
> 13:02 Zoffix That's got broke
This seems very related:
m: sub foo (*@foo) { dd @foo[1] = 42 }; foo ; foo |;
rakudo-moar 88140b: OUTPUT: «42Cannot modify an immutable Str in
sub foo at line 1 in block at line 1»
It actually affects whether values in a created Map are mutable, *depending on
how the Map was cre
This seems very related:
m: sub foo (*@foo) { dd @foo[1] = 42 }; foo ; foo |;
rakudo-moar 88140b: OUTPUT: «42Cannot modify an immutable Str in
sub foo at line 1 in block at line 1»
It actually affects whether values in a created Map are mutable, *depending on
how the Map was cre
On Mon, 17 Apr 2017 09:53:28 -0700, mt1...@gmail.com wrote:
> Since I've installed perl6 version 2017.03-234-g0ebdaa4 built on MoarVM
> version 2017.03-128-gc9ab59c, several modules are experiencing failures
> when using the following construct (golfed down)(I am sure that the
> module loads)
>
1 - 100 of 1105 matches
Mail list logo
