On Mon, 18 Sep 2017 07:26:39 -0700, c...@zoffix.com wrote:
> The .perl of a default Hash correctly shows when the hash has been
> scalarized:
>
> $ perl6 -e 'my %h := {:42a}; my $h = %h; say %h.perl; say $h.perl'
> {:a(42)}
> ${:a(42)}
>
>
> However, the same distinction does not show up when us
On Mon, 18 Sep 2017 07:26:39 -0700, c...@zoffix.com wrote:
> The .perl of a default Hash correctly shows when the hash has been
> scalarized:
>
> $ perl6 -e 'my %h := {:42a}; my $h = %h; say %h.perl; say $h.perl'
> {:a(42)}
> ${:a(42)}
>
>
> However, the same distinction does not show up when us
On Wed, 05 Aug 2015 10:06:17 -0700, jdv79 wrote:
> Hello,
>
> I recently tried to make a custom array type so that I could
> type the values. My intent would be that it would act like
> an array in all ways except have the value typing.
>
> I tried delegating to * but that doesn't work because A
On Sat, 16 Sep 2017 08:46:00 -0700, barto...@gmx.de wrote:
> Here is a simple example:
>
> $ ./perl6-j -e 'try { die "foo" }; say $!.perl; say $!.gist'
> X::AdHoc.new(payload => "foo")
> Died
> in block at -e line 1
It looks like the 'Died' stems from this line:
https://github.com/perl6/nqp/
On Thu, 19 Jun 2014 17:45:23 -0700, elizabeth wrote:
> Additional finds:
>
> [19:24:52] m: my @a; my $c = 1; @a.push: $($c,1); $c =
> "hi"; @a.push: $($c,2); say @a.perl
> [19:24:53] <+camelia>rakudo-moar 8812ca: OUTPUT«Array.new($("hi",
> 1), $("hi", 2))»
> [19:25:09] it would appear
On Mon, 18 Sep 2017 09:46:50 -0700, sml...@gmail.com wrote:
> This ticket can IMO be closed as 'rejected', but I'll leave it open
> for now in case I missed something obvious or in case you want to turn
> it into an RFC or similar.
>
>
> ---
> [1] http://design.perl6.org/S05.html#Subpattern_captu
On Mon, 18 Sep 2017 09:46:50 -0700, sml...@gmail.com wrote:
> This ticket can IMO be closed as 'rejected', but I'll leave it open
> for now in case I missed something obvious or in case you want to turn
> it into an RFC or similar.
>
>
> ---
> [1] http://design.perl6.org/S05.html#Subpattern_captu
> On 18 Sep 2017, at 19:45, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132121]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132121 >
>
>
> Apparently i
> On 18 Sep 2017, at 19:45, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132121]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132121 >
>
>
> Apparently i
On Mon, 18 Sep 2017 10:45:21 -0700, c...@zoffix.com wrote:
> Apparently it's possible to assign to capture variables to change what
> the resultant Match will have.
>
> The first question: is this actually something specced and supported?
> Especially the fact that further captures continue their
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132121]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132121 >
Apparently it's possible to assign to capture variables to change what the
resultant Matc
> "note" is the same thing as "say", but to the std error:
Er, I was referring more to the P5 behaviour of warn() - w/o a newline, its
output, to stderr, included more info:
$ perl -e 'warn("hi mom")' > /dev/null
hi mom at -e line 1.
$ perl -e 'warn("hi mom\n")' > /dev/null
hi mom
"note" appe
There was a little bit of progress with this here:
https://github.com/MoarVM/MoarVM/pull/687
On 2017-09-01 12:53:36, alex.jakime...@gmail.com wrote:
> https://irclog.perlgeek.de/perl6-dev/2017-09-01#i_15102810
>
> On 2017-07-31 08:27:09, alex.jakime...@gmail.com wrote:
> > FWIW, still happens afte
On Mon, 18 Sep 2017 09:00:54 -0700, c...@zoffix.com wrote:
> IRC: https://irclog.perlgeek.de/perl6/2017-09-18#i_15181575
>
> We can use $0 here to refer to previous capture and regex matches:
> m: say "11" ~~ /(\d)[$0]/
> rakudo-moar 48a84d: OUTPUT: «｢11｣ 0 => ｢1｣»
>
> But if we capture
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132120]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132120 >
IRC: https://irclog.perlgeek.de/perl6/2017-09-18#i_15181575
We can use $0 here to refer t
On Mon, 18 Sep 2017 07:44:16 -0700, elizabeth wrote:
> Fixed with 66c2d05f29 , tests need attention in S03-operators/eqv.t
>
> > On 18 Sep 2017, at 14:51, Zoffix Znet (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Zoffix Znet
> > # Please include the string: [perl #132117]
On Mon, 18 Sep 2017 07:44:16 -0700, elizabeth wrote:
> Fixed with 66c2d05f29 , tests need attention in S03-operators/eqv.t
>
> > On 18 Sep 2017, at 14:51, Zoffix Znet (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Zoffix Znet
> > # Please include the string: [perl #132117]
Closing this myself in favor of this ticket:
https://github.com/perl6/doc/issues/1567
On 2017-07-17 23:51:21, alex.jakime...@gmail.com wrote:
> Alright, it seems that rakudo is not entirely incorrect here. See this
> discussion: https://irclog.perlgeek.de/perl6-dev/2017-07-18#i_14885863
>
> TL;DR,
Fixed with 66c2d05f29 , tests need attention in S03-operators/eqv.t
> On 18 Sep 2017, at 14:51, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132117]
> # in the subject line of all future correspondence about this issue.
> # http
Fixed with 66c2d05f29 , tests need attention in S03-operators/eqv.t
> On 18 Sep 2017, at 14:51, Zoffix Znet (via RT)
> wrote:
>
> # New Ticket Created by Zoffix Znet
> # Please include the string: [perl #132117]
> # in the subject line of all future correspondence about this issue.
> # http
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132119]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132119 >
The .perl of a default Hash correctly shows when the hash has been scalarized:
$ perl
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132117]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132117 >
If you `eqv` two lazy Seqs, you get a useful error:
m: say (lazy 1,) eqv (lazy 1,)
Thanks!
2017-09-18 4:12 GMT+02:00 :
> I’ve added you to the repository – sorry about the delay, and thanks for
> the help with the module!
>
>
>
> *From: *JJ Merelo
> *Sent: *Sunday, September 17, 2017 4:51 AM
> *To: *and...@egeler.us
> *Cc: *perl6-us...@perl.org
> *Subject: *Offering my help wi
> On 18 Sep 2017, at 04:39, Brian S. Julin via RT
> wrote:
>
> On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote:
>> More comments on similar issue: https://irclog.perlgeek.de/perl6/2017-
>> 09-17#i_15176823
>>
>> Basically, a lot of core constructs aren't workable with user-land
>> su
> On 18 Sep 2017, at 04:39, Brian S. Julin via RT
> wrote:
>
> On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote:
>> More comments on similar issue: https://irclog.perlgeek.de/perl6/2017-
>> 09-17#i_15176823
>>
>> Basically, a lot of core constructs aren't workable with user-land
>> su
25 matches
Mail list logo
