On Fri, 29 Dec 2017 07:05:29 -0800, sml...@gmail.com wrote:
> These regexes parse and run fine (they match a single `#` character):
>
> /\#/;
> /^\#/;
>
> But this one doesn't:
>
> /^ \#/;
>
> The error thrown, is:
>
> ===SORRY!===
> Regex not terminated.
> at -e:1
>
On Fri, 29 Dec 2017 07:05:29 -0800, sml...@gmail.com wrote:
> These regexes parse and run fine (they match a single `#` character):
>
> /\#/;
> /^\#/;
>
> But this one doesn't:
>
> /^ \#/;
>
> The error thrown, is:
>
> ===SORRY!===
> Regex not terminated.
> at -e:1
>
On Tue, 02 May 2017 08:35:34 -0700, c...@zoffix.com wrote:
> Both of these forms produce the error below
>
> my %stuff = ;
> say 'foo bar meows' ~~ m:g/ %stuff\S+ /;
> say 'foo bar meows' ~~ m:g/ %() \S+ /;
>
> # P6opaque: no such attribute '$!reified' in type List when trying to
> get
>
# New Ticket Created by Sam S.
# Please include the string: [perl #132666]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132666 >
These regexes parse and run fine (they match a single `#` character):
/\#/;
/^\#/;
On Wed, 27 Dec 2017 05:17:34 -0800, c...@zoffix.com wrote:
> On Mon, 28 Nov 2016 05:41:48 -0800, c...@zoffix.com wrote:
> > On Mon, 28 Nov 2016 05:38:23 -0800, c...@zoffix.com wrote:
> > > The error is even weirder here:
> > >
> > > m: package IO::Foo { }; use IO::Foo
> > > rakudo-moar 054aca:
On Wed, 27 Dec 2017 05:17:34 -0800, c...@zoffix.com wrote:
> On Mon, 28 Nov 2016 05:41:48 -0800, c...@zoffix.com wrote:
> > On Mon, 28 Nov 2016 05:38:23 -0800, c...@zoffix.com wrote:
> > > The error is even weirder here:
> > >
> > > m: package IO::Foo { }; use IO::Foo
> > > rakudo-moar 054aca:
On Mon, 28 Nov 2016 05:41:48 -0800, c...@zoffix.com wrote:
> On Mon, 28 Nov 2016 05:38:23 -0800, c...@zoffix.com wrote:
> > The error is even weirder here:
> >
> > m: package IO::Foo { }; use IO::Foo
> > rakudo-moar 054aca: OUTPUT«===SORRY!===»
>
> Oh, that one was just a glitch in camelia. The
On Mon, 28 Nov 2016 05:41:48 -0800, c...@zoffix.com wrote:
> On Mon, 28 Nov 2016 05:38:23 -0800, c...@zoffix.com wrote:
> > The error is even weirder here:
> >
> > m: package IO::Foo { }; use IO::Foo
> > rakudo-moar 054aca: OUTPUT«===SORRY!===»
>
> Oh, that one was just a glitch in camelia. The
On Tue, Dec 26, 2017 at 12:15 AM, Brandon Allbery via RT <
perl6-bugs-follo...@perl.org> wrote:
> IIRC this is known, and not really fixable. It's not even cmd.exe but a
> Windows console mode limitation.
>
Come to think of it, there should be existing mention of this on the moa
On Mon, Dec 25, 2017 at 1:07 AM, Zoffix Znet via RT <
perl6-bugs-follo...@perl.org> wrote:
> On Thu, 16 Nov 2017 09:53:46 -0800, c...@zoffix.com wrote:
> > On 2017.07 on Win7 with 65001 code page enabled, the » char doesn't
> > show up at all. Just seems to get removed from t
On Thu, 16 Nov 2017 09:53:46 -0800, c...@zoffix.com wrote:
> On 2017.07 on Win7 with 65001 code page enabled, the » char doesn't
> show up at all. Just seems to get removed from the content if I paste
> it into the terminal.
Starting to think this might be a limitation of cmd.exe. Though
On Thu, 16 Nov 2017 09:53:46 -0800, c...@zoffix.com wrote:
> On 2017.07 on Win7 with 65001 code page enabled, the » char doesn't
> show up at all. Just seems to get removed from the content if I paste
> it into the terminal.
Starting to think this might be a limitation of cmd.exe. Though
# New Ticket Created by Tom Browder
# Please include the string: [perl #132650]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132650 >
Given this nqp code:
=begin comment
some code
...
=begin comment
On Tue, 22 Mar 2016 07:10:54 -0700, elizabeth wrote:
>
> > On 21 Mar 2016, at 16:41, Elizabeth Mattijsen (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Elizabeth Mattijsen
> > # Please include the string: [perl #127756]
> &
On Tue, 22 Mar 2016 07:10:54 -0700, elizabeth wrote:
>
> > On 21 Mar 2016, at 16:41, Elizabeth Mattijsen (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Elizabeth Mattijsen
> > # Please include the string: [perl #127756]
> &
I reproduced this in our own test suite. Reported on
https://github.com/rakudo/rakudo/issues/1332
(gonna close this ticket in favour of that Issue)
> It works, but occasionally throws:
Note that it's a warning, not an exception.
You can work-around this bug with `andthen` operator: `(require
I reproduced this in our own test suite. Reported on
https://github.com/rakudo/rakudo/issues/1332
(gonna close this ticket in favour of that Issue)
> It works, but occasionally throws:
Note that it's a warning, not an exception.
You can work-around this bug with `andthen` operator: `(require
Fudge removed in https://github.com/perl6/roast/commit/b41e6a0e61ab501d7e5cf9d5
Fudge removed in https://github.com/perl6/roast/commit/b41e6a0e61ab501d7e5cf9d5
# New Ticket Created by Tom Browder
# Please include the string: [perl #132632]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132632 >
The following pod configuration value formats are NYI:
Type Example
# New Ticket Created by
# Please include the string: [perl #132611]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132611 >
On Tue, Dec 19, 2017 at 02:02:50PM +0100, pe...@6dof.xyz wrote:
> I golfed the problem down to:
>
>
This works now as expected:
m: sub Foo(uint32 :$bar) { say $bar }; Foo(:bar(4))
rakudo-moar ae6177ca2: OUTPUT: «4»
I think, it was fixed with https://github.com/perl6/nqp/commit/fc727ea911
(bisectable pointed to the corresponding NQP bump).
Since the tests in S02-types/native.t are
# New Ticket Created by Curt Tilmes
# Please include the string: [perl #132592]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132592 >
Under these exact circumstances, I reliably get an error. (Including the
inclusion of
FWIW this issue was noticed today:
https://irclog.perlgeek.de/perl6/2017-12-16#i_15587006
On 2016-04-11 20:40:43, ddgr...@gmail.com wrote:
> '@array[0, 3, 7]' is much slower than '(@array[0], @array[3], @array[7])'
>
>
> time perl6 -e 'my @a = ^500;my @f;my $s = @a.elems;loop (my $i1 = 0; $i1 <
>
I am pretty sure that this commit is relevant to this issue:
https://github.com/rakudo/rakudo/commit/fc52143beee3178c7f39d770f95c7d60b2a1a1e4
On 2017-10-07 17:20:37, alex.jakime...@gmail.com wrote:
> Zoffix++ pointed out that there is a problem with IntStr also:
>
> Code:
> enum Foo (:Bar(1),
# New Ticket Created by Dan Zwell
# Please include the string: [perl #132585]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132585 >
The output of a hash of hashes of ints looks my Hash[Int] %nested-type;
; bug
> > goes back to at least 2015.12.
> >
> > On Wed, Dec 13, 2017 at 11:56 PM Zoffix Znet via RT <
> > perl6-bugs-follo...@perl.org> wrote:
> >
> > > On Wed, 06 Dec 2017 01:59:42 -0800, d...@zwell.net wrote:
> > > > A git bisec
roduce, and using that test case, I found this bug
> goes back to at least 2015.12.
>
> On Wed, Dec 13, 2017 at 11:56 PM Zoffix Znet via RT <
> perl6-bugs-follo...@perl.org> wrote:
>
> > On Wed, 06 Dec 2017 01:59:42 -0800, d...@zwell.net wrote:
> > > A git bis
Thanks for finding that. Can we close this duplicate bug? Issue #128287 has
stronger steps to reproduce, and using that test case, I found this bug
goes back to at least 2015.12.
On Wed, Dec 13, 2017 at 11:56 PM Zoffix Znet via RT <
perl6-bugs-follo...@perl.org> wrote:
> On Wed, 06 De
By the way, there is a pull request: https://github.com/rakudo/rakudo/pull/1020
But the work on it is kinda stalled.
On 2017-02-17 04:22:51, alex.jakime...@gmail.com wrote:
> Reopened for now.
>
> See RT #121807 and RT #125371 for more info. Basically, there will be
> no error
> after I'm done
On Wed, 13 Dec 2017 19:23:38 -0800, c...@zoffix.com wrote:
> Also affects some methods:
>
> m: my %h; say %h.AT-KEY: 1|2
> rakudo-moar eaf609edb: OUTPUT: «Type check failed in binding
> to parameter ''; expected Callable but got Method+{is-nodal}
> (Method+{is-nodal}.new) in block at line
On Wed, 13 Dec 2017 19:23:38 -0800, c...@zoffix.com wrote:
> Also affects some methods:
>
> m: my %h; say %h.AT-KEY: 1|2
> rakudo-moar eaf609edb: OUTPUT: «Type check failed in binding
> to parameter ''; expected Callable but got Method+{is-nodal}
> (Method+{is-nodal}.new) in block at line
On Tue, 14 Jul 2015 22:32:47 -0700, elizabeth wrote:
>
> > On 14 Jul 2015, at 12:29, Carl Mäsak (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by "Carl Mäsak"
> > # Please include the string: [perl #125614]
> > # in th
On Tue, 14 Jul 2015 22:32:47 -0700, elizabeth wrote:
>
> > On 14 Jul 2015, at 12:29, Carl Mäsak (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by "Carl Mäsak"
> > # Please include the string: [perl #125614]
> > # in th
On Mon, 13 Nov 2017 07:31:44 -0800, alex.jakime...@gmail.com wrote:
> Unfortunately there's no easy way to know how many elements are there. If I
> recall correctly, stringy ranges may loop forever due to normalization and
> other things.
Can't think of anything reasonable either, especially
On Mon, 01 Jun 2015 05:41:01 -0700, drf...@pobox.com wrote:
> I'm not even sure if the error text is correct, come to think of it. I'd
> think that a leading '=' outside of a here-doc or multi-line string
> regardless of q/qq/Q<[[ variant should be treated as a POD comment, so I
> would expect
On Mon, 01 Jun 2015 05:41:01 -0700, drf...@pobox.com wrote:
> I'm not even sure if the error text is correct, come to think of it. I'd
> think that a leading '=' outside of a here-doc or multi-line string
> regardless of q/qq/Q<[[ variant should be treated as a POD comment, so I
> would expect
On Sat, 30 Sep 2017 12:45:09 -0700, sjn-perl...@pvv.org wrote:
> I think this bug can be closed.
Agreed. Rejecting.
I see little reason to muddy up the Usage even more with type information,
where you're mostly limited to Int/Str types anyway, and variable name
helps know which to use.
The
On Sat, 30 Sep 2017 12:45:09 -0700, sjn-perl...@pvv.org wrote:
> I think this bug can be closed.
Agreed. Rejecting.
I see little reason to muddy up the Usage even more with type information,
where you're mostly limited to Int/Str types anyway, and variable name
helps know which to use.
The
On Sat, 02 Dec 2017 20:41:05 -0800, alex.jakime...@gmail.com wrote:
> Isn't it implemented as :update now?
> https://docs.perl6.org/routine/open
Yes, :update is it. Tests:
https://github.com/perl6/roast/blob/master/S32-io/open.t#L68-L92
>
> Or maybe you can even use :mode? (the
On Sat, 02 Dec 2017 20:41:05 -0800, alex.jakime...@gmail.com wrote:
> Isn't it implemented as :update now?
> https://docs.perl6.org/routine/open
Yes, :update is it. Tests:
https://github.com/perl6/roast/blob/master/S32-io/open.t#L68-L92
>
> Or maybe you can even use :mode? (the
On Sat, 09 Dec 2017 15:26:25 -0800, c...@zoffix.com wrote:
> On Sat, 09 Dec 2017 13:19:23 -0800, elizabeth wrote:
> > If that shouldn’t work, or work differently, it can be ripped
> > out / replaced. If that should work, then we need to look at fixing
> > -put-.
>
> IMO it should work,
On Sat, 09 Dec 2017 15:26:25 -0800, c...@zoffix.com wrote:
> On Sat, 09 Dec 2017 13:19:23 -0800, elizabeth wrote:
> > If that shouldn’t work, or work differently, it can be ripped
> > out / replaced. If that should work, then we need to look at fixing
> > -put-.
>
> IMO it should work,
Just for the records: As far as I can tell, the bug that caused the above
failures was an "off by one" in the multi cache implementation. It was fixed
with https://github.com/perl6/nqp/commit/7eaebf5abd
the type system.
>
> On Fri, Dec 1, 2017 at 6:00 PM perl6 via RT follo...@perl.org>
> wrote:
>
> > Greetings,
> >
> > This message has been automatically generated in response to the
> > creation of a trouble ticket regarding:
> > "[BUG
the type system.
>
> On Fri, Dec 1, 2017 at 6:00 PM perl6 via RT follo...@perl.org>
> wrote:
>
> > Greetings,
> >
> > This message has been automatically generated in response to the
> > creation of a trouble ticket regarding:
> > "[BUG
On Sat, 07 Oct 2017 17:36:28 -0700, alex.jakime...@gmail.com wrote:
> Oops. Last link:
> https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e4555ded27cba91/src/Perl6/Grammar.nqp#L3853
>
> On 2017-10-07 17:35:58, alex.jakime...@gmail.com wrote:
> > FWIW to add it one will need to hack
On Sat, 07 Oct 2017 17:36:28 -0700, alex.jakime...@gmail.com wrote:
> Oops. Last link:
> https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e4555ded27cba91/src/Perl6/Grammar.nqp#L3853
>
> On 2017-10-07 17:35:58, alex.jakime...@gmail.com wrote:
> > FWIW to add it one will need to hack
There was indeed something wrong with the multi cache on the JVM backend. Fixed
with https://github.com/perl6/nqp/commit/7eaebf5abd
I'm closing this ticket as 'resolved'.
There was something wrong with the multi cache on the JVM backend. Fixed with
https://github.com/perl6/nqp/commit/7eaebf5abd
I'm closing this ticket as 'resolved'.
There was indeed something wrong with the multi cache on the JVM backend. Fixed
with https://github.com/perl6/nqp/commit/7eaebf5abd
I'm closing this ticket as 'resolved'.
On Tue, 28 Mar 2017 07:38:32 -0700, c...@zoffix.com wrote:
>
> The last two items printed, `$type` and `$speedup`, get set properly
> if used in a sub's signature:
>
> `sub`
> 14:34 m: sub ($sha, $, $, *@rest ($, $type, $speedup,
> $)) {dd [ @rest, $type, $speedup ];}(|'fa9aa47 [io
On Tue, 28 Mar 2017 07:38:32 -0700, c...@zoffix.com wrote:
>
> The last two items printed, `$type` and `$speedup`, get set properly
> if used in a sub's signature:
>
> `sub`
> 14:34 m: sub ($sha, $, $, *@rest ($, $type, $speedup,
> $)) {dd [ @rest, $type, $speedup ];}(|'fa9aa47 [io
On Mon, 07 Aug 2017 15:34:26 -0700, c...@zoffix.com wrote:
> Originally taken from:
> https://stackoverflow.com/questions/45527881/why-does-and-affect-perl-
> 6-junctions-differently
>
> For example, there's a difference between output of using `+` and
> using `~` with a Junction. With `+` you
On Mon, 07 Aug 2017 15:34:26 -0700, c...@zoffix.com wrote:
> Originally taken from:
> https://stackoverflow.com/questions/45527881/why-does-and-affect-perl-
> 6-junctions-differently
>
> For example, there's a difference between output of using `+` and
> using `~` with a Junction. With `+` you
On Sat, 02 Dec 2017 15:36:40 -0800, alex.jakime...@gmail.com wrote:
> lizmat:
> > Fixed with cd24b1c55d0c798c8fd776f , tests needed (also for OUTERS::)
>
> 「testneeded」
>
> On 2017-12-02 04:06:41, alex.jakime...@gmail.com wrote:
> > Still reproducible (2017.11, HEAD(5929887)) on MoarVM.
> >
> >
On Sat, 02 Dec 2017 15:36:40 -0800, alex.jakime...@gmail.com wrote:
> lizmat:
> > Fixed with cd24b1c55d0c798c8fd776f , tests needed (also for OUTERS::)
>
> 「testneeded」
>
> On 2017-12-02 04:06:41, alex.jakime...@gmail.com wrote:
> > Still reproducible (2017.11, HEAD(5929887)) on MoarVM.
> >
> >
On Mon, 11 Dec 2017 20:30:18 -0800, c...@zoffix.com wrote:
> The form with space wasn't implemented.
>
> It is now: https://github.com/rakudo/rakudo/commit/c0f99a393b
Never mind. Decided to revert that form (
https://github.com/rakudo/rakudo/commit/2f955d55e3 )
The `:()` form is actually a
On Mon, 11 Dec 2017 20:30:18 -0800, c...@zoffix.com wrote:
> The form with space wasn't implemented.
>
> It is now: https://github.com/rakudo/rakudo/commit/c0f99a393b
Never mind. Decided to revert that form (
https://github.com/rakudo/rakudo/commit/2f955d55e3 )
The `:()` form is actually a
On Sat, 02 Dec 2017 05:19:45 -0800, alex.jakime...@gmail.com wrote:
> Yeah. It was resolved here I think: (2014-12-08)
> https://github.com/rakudo/rakudo/commit/fbc87d2a6bbfc4899b0740119ac8696cc27f1f59
>
> 「testneeded」
>
> On 2014-12-09 04:54:08, r...@hoelz.ro wrote:
> > On Sun Dec 07 07:41:52
On Sat, 02 Dec 2017 05:19:45 -0800, alex.jakime...@gmail.com wrote:
> Yeah. It was resolved here I think: (2014-12-08)
> https://github.com/rakudo/rakudo/commit/fbc87d2a6bbfc4899b0740119ac8696cc27f1f59
>
> 「testneeded」
>
> On 2014-12-09 04:54:08, r...@hoelz.ro wrote:
> > On Sun Dec 07 07:41:52
# New Ticket Created by Timothy Smith
# Please include the string: [perl #132570]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132570 >
Save make-testcase.sh in /tmp, and:
rm -rf ./invalid-typename-bug; sh make-testcase.sh
Closing this ticket in favor of this one:
https://github.com/rakudo/rakudo/issues/1304
On 2017-12-01 11:03:43, alex.jakime...@gmail.com wrote:
> Still failing (2017.11, HEAD(5929887))
>
> On 2014-07-31 13:05:19, david.warring wrote:
> > I've added some fudged tests to S03-operators/relational.t.
Tests: https://github.com/perl6/roast/commit/786472ae43
Tests: https://github.com/rakudo/rakudo/commit/20d67a3d4d
Tests: https://github.com/rakudo/rakudo/commit/20d67a3d4d
On Mon, 23 Oct 2017 05:28:04 -0700, c...@zoffix.com wrote:
> This code produces an LTA error:
>
> my %days := SetHash.new: Date.today … Date.new: '2030-04-02';
> %days ∖= %days.grep: *.key.day-of-week > 5;
>
> First, the error reads "Cannot modify an immutable SetHash" which is
> confusing,
>
On Mon, 23 Oct 2017 05:28:04 -0700, c...@zoffix.com wrote:
> This code produces an LTA error:
>
> my %days := SetHash.new: Date.today … Date.new: '2030-04-02';
> %days ∖= %days.grep: *.key.day-of-week > 5;
>
> First, the error reads "Cannot modify an immutable SetHash" which is
> confusing,
>
On Fri, 29 Sep 2017 09:07:40 -0700, c...@zoffix.com wrote:
> - Seq.skip mutates the invocant:
No longer. It now consumes the iterator, which aligns the behaviour with
Any.skip.
Fixed by lizmat++ in https://github.com/rakudo/rakudo/commit/854c10c27e
Tests:
On Fri, 29 Sep 2017 09:07:40 -0700, c...@zoffix.com wrote:
> - Seq.skip mutates the invocant:
No longer. It now consumes the iterator, which aligns the behaviour with
Any.skip.
Fixed by lizmat++ in https://github.com/rakudo/rakudo/commit/854c10c27e
Tests:
Recommend merging with RT 125398 - "no strict temp does not autcreate hashes
and hash elements"
Also seems fixed by e5b49ce and could be expected to share same cause of
"...the underlying issue is that the default value of container descriptors
created automatically with “no strict” are Mu
Fixed in
https://github.com/rakudo/rakudo/commit/2cd266fe08aa386b180dda14c15659c360623c99
Tests in
https://github.com/perl6/roast/commit/3ae26405385d5e496b401326e3252294b8a5785b
and
https://github.com/perl6/roast/commit/bc48eed6849cbbb873320052cb78a6e57b9c4a2a
tbrowder++
On 2015-11-26 11:33:47,
On Sat, 09 Dec 2017 13:19:23 -0800, elizabeth wrote:
> If that shouldn’t work, or work differently, it can be ripped
> out / replaced. If that should work, then we need to look at fixing
> -put-.
IMO it should work, considering you can't nqp::unbox_n/nqp::unbox_i Junctions
either, yet we don't
On Sat, 09 Dec 2017 13:19:23 -0800, elizabeth wrote:
> If that shouldn’t work, or work differently, it can be ripped
> out / replaced. If that should work, then we need to look at fixing
> -put-.
IMO it should work, considering you can't nqp::unbox_n/nqp::unbox_i Junctions
either, yet we don't
> On 8 Dec 2017, at 19:21, Zoffix Znet via RT <perl6-bugs-follo...@perl.org>
> wrote:
>
> On Fri, 08 Dec 2017 08:28:32 -0800, comdog wrote:
>> This comes from an answer to a Perl 6 question on Stackoverflow that
>> showed a different bug:
>>
>>ht
On Fri, 08 Dec 2017 08:28:32 -0800, comdog wrote:
> This comes from an answer to a Perl 6 question on Stackoverflow that
> showed a different bug:
>
> https://stackoverflow.com/q/45527881/2766176
>
> With put() it does not and gives a strange error:
I guess jnthn++ gets a score point for
On Fri, 08 Dec 2017 08:28:32 -0800, comdog wrote:
> This comes from an answer to a Perl 6 question on Stackoverflow that
> showed a different bug:
>
> https://stackoverflow.com/q/45527881/2766176
>
> With put() it does not and gives a strange error:
I guess jnthn++ gets a score point for
On Thu, 07 Dec 2017 15:48:35 -0800, comdog wrote:
> I first asked about this on Stackoverflow:
>
> https://stackoverflow.com/q/47704428/2766176
>
> A .tail on a .tail appears to do the wrong thing:
>
> > my $list = ;
> (a b c d e f g h i j)
>
> > $list.tail(5).tail
> Nil
>
> But throwing a
On Thu, 07 Dec 2017 15:48:35 -0800, comdog wrote:
> I first asked about this on Stackoverflow:
>
> https://stackoverflow.com/q/47704428/2766176
>
> A .tail on a .tail appears to do the wrong thing:
>
> > my $list = ;
> (a b c d e f g h i j)
>
> > $list.tail(5).tail
> Nil
>
> But throwing a
rakudo#1296 could replace this one.
2017-12-03 14:10 GMT+08:00 陈梓立 :
> Now the issue is quite different.
>
> I think it becomes an issue about `but`, not about `Cannot convert string
> to number`
>
Now the issue is quite different.
I think it becomes an issue about `but`, not about `Cannot convert string
to number`
Note that if you call `next`, then the order is correct.
This is not limited in operator overloading
```
my $a;
$a := { $^a + $^b }
# ok
```
```
my
:= { $^a + $^b }
# Cannot use bind operator with this left-hand side
```
```
my := { $^a + $^b }
say a(1, 2)
# 3
```
```
my : := { $^a + $^b };
say 1 plus 2 plus 3
# 6
```
Note that it is all well
1. now it's moved to S06-operator-overloading/infix.t
2. note that default Left-associative works, this ticket in fact about
reserved words. See the example below:
```
{
my sub infix: ($a, $b) {
$a ** $b;
}
is (2 Z 1 Z 2), 4, "default Left-associative works.";
}
# Calling infix:(Int,
So far we've fix the bugs on NEXT and LAST, while POST remained.
I added a test for this ticket perl6/roast#362
A git bisect showed that this error began in commit
22b4ef05b1f72b50d63e4599d5e037bccf1f08ed, but there must be have been an
underlying problem that was already present, since this commit did not
change the type system.
On Fri, Dec 1, 2017 at 6:00 PM perl6 via RT <perl6-bugs-follo...@perl.
FWIW it never worked:
https://gist.github.com/Whateverable/d9dbebb0e985a3964845df2c8652cbdf
On 2017-11-27 17:36:22, comdog wrote:
> I previously asked about this unexpected Z behavior on Stackoverflow
> ( https://stackoverflow.com/q/45001820/2766176 ).
>
> I expected this to change several hash
Some *able info, if anyone is interested:
Output on all releases:
https://gist.github.com/a68b094519839b939f8c70d66a80d8c0
Some possibly relevant commits:
https://github.com/rakudo/rakudo/commit/92bd7e4f54a92fa660f99b4d056d33a08fb98bd2
Properly fixed with e5b49ce , tests needed for container type / default value
of auto-defined
variables.
> On 3 Dec 2017, at 04:45, Aleks-Daniel Jakimenko-Aleksejev via RT
> <perl6-bugs-follo...@perl.org> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
>
research.
Either this ticket should remain open, or we should create another issue for
this.
> On 3 Dec 2017, at 04:45, Aleks-Daniel Jakimenko-Aleksejev via RT
> <perl6-bugs-follo...@perl.org> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-06-13 05:48:13, ron
, 2017 at 6:00 AM, Aleks-Daniel Jakimenko-Aleksejev via RT <
perl6-bugs-follo...@perl.org> wrote:
> Hmmm… Parrot is in the past as of today, and I wish it was possible to try
> this
> on MoarVM. What's the way to reproduce this issue?
>
> On 2014-07-14 02:31:54, teodozjan wrote
# New Ticket Created by Dan Zwell
# Please include the string: [perl #132531]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132531 >
I just checked, and got the same result on Rakudo version 2017.11 built on
MoarVM version
On Sat, 26 Dec 2015 14:27:04 -0800, autarch wrote:
> There's a class in rakudo's Pod.pm named Pod::Raw, but rakudo does not
> produce these blocks. I'm not sure whether the bug is that the class
> exists or that it's never used.
I *think* it's meant to be Pod::Block::Comment. In
On Tue, 28 Nov 2017 12:35:42 -0800, barto...@gmx.de wrote:
> [...]
> I tried to golf the failures from set_addition.t and found the
> following:
>
> $ ./perl6-j --ll-exception -e ':<(+)>(SetHash.new, SetHash.new,
> SetHash.new); :<(+)>(|(Set.new, Set.new, Set.new));
> :<(+)>(|(Set.new, Set.new,
around
of binding.
> On 3 Dec 2017, at 11:23, Aleks-Daniel Jakimenko-Aleksejev via RT
> <perl6-bugs-follo...@perl.org> wrote:
>
> As of today (2017.11,HEAD(e5b660e)) it prints this:
>
> Cannot call method 'new' on a null object
> in block at -e line 1
>
> Which i
So is the current behavior good or bad?
On 2014-10-15 05:16:27, barto...@gmx.de wrote:
> The current behaviour is:
>
> $ perl6-m -e 'my %h{Any}; %h=Any; %h //= "a"; say %h.perl'
> Hash[Any,Any].new("a" => "a")
>
> $ perl6-m -e 'my %h{Any}; %h //= "a"; say %h.perl'
> Hash[Any,Any].new("a" => "a")
On Sat, 28 Feb 2015 07:45:31 -0800, b...@abrij.org wrote:
> (10:19:08 AM) skids: m: role g[::T $t] { multi method foo (T $a) {
> "OHAI".say }; multi method foo($a) { "ONOES".say }; };
> g[Int(Str)].new.foo("100")
> (10:19:09 AM) camelia: rakudo-moar 35de75: OUTPUT«ONOES»
> (10:20:59 AM) jnthn:
Still NYI (2017.11,HEAD(e5b660e))
On 2014-10-14 01:02:45, masak wrote:
> m: grammar Test { token TOP { }; proto token
> Foo(Int) {*}; token Foo:sym(Int $a) { "a" }; token Foo:sym(Int
> $a) { "b" } }; say Test.parse("a");
> rakudo-moar 8b3e8c: OUTPUT«Too few positionals passed;
>
Seems to be reproducible (2017.11,HEAD(e5b660e))
On 2014-10-16 13:43:34, masak wrote:
> camelia was having some indigestion in the below backlog, which is why
> I'm reporting some local evals (from "This is perl6 version
> 2014.09-202-g8b3e8c2 built on MoarVM version 2014.09-54-g03ac9a7").
>
>
Still reproducible (2017.11,HEAD(e5b660e))
On 2015-05-15 11:25:07, jdv79 wrote:
> The first example there should have been:
>
> [jdv@wieldy ~]$ perl6 -e 'role Foo[::T] { has Int @.a }; say
> Foo[Int].new.a.WHAT'
> (Array[Int])
> [jdv@wieldy ~]$ perl6 -e 'role Foo[::T] { has T @.a }; say
>
501 - 600 of 16765 matches
Mail list logo