# New Ticket Created by mt1957
# Please include the string: [perl #131493]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131493 >
Hi,
In Rakudo version 2017.05-338-gaca1929 built on MoarVM version
2017.05-25-g62bc54e
implem
Well,
say IntStr ~~ Str # True
In other words, IntStr *is* a Str.
What I find interesting, however, is this difference:
sub s (Str() :$str) {say $str.WHAT}; s(:str<1>) # IntStr
sub s (Str :$str) {say $str.Str.WHAT}; s(:str<1>) # Str
I would have expected the same output in both cases.
On 2017
# New Ticket Created by Benjamin Goldberg
# Please include the string: [perl #131495]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131495 >
The code in this gist:
https://gist.github.com/BenGoldberg1/19e6e8b70cc5c838a15d72e
On 06/03/2017 11:36 AM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
> say IntStr ~~ Str
> say Str ~~ IntStr
False
On 06/03/2017 11:36 AM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
say IntStr ~~ Str
> say Str ~~ IntStr
False
On 06/03/2017 11:36 AM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
sub s (Str() :$str) {say $str.WHAT}; s(:str<1>) # IntStr
sub s (Str :$str) {say $str.Str.WHAT}; s(:str<1>) # Str
I think the last one is coerced explicitly. Btw I didn't know about
'Str() :$str' specification. What does it
On 06/03/2017 11:36 AM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
> sub s (Str() :$str) {say $str.WHAT}; s(:str<1>) # IntStr
> sub s (Str :$str) {say $str.Str.WHAT}; s(:str<1>) # Str
I think the last one is coerced explicitly. Btw I didn't know about
'Str() :$str' specification. What does it
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131496]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131496 >
Handled Failures are explosive again, if they're .perl'ed:
m: given Failure.new { .s
# New Ticket Created by Itsuki Toyota
# Please include the string: [perl #131498]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131498 >
See the following codes and results:
$ perl6 -e 'class A { multi method f(:$vert!, Code
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131499]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131499 >
In none of these cases is the use of variables actually useless:
m: my ($sensor1, $senso
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131500]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131500 >
Using loose ops works fine some times:
m: say (Int andthen 42)
rakudo-moar 64e8
After some discussion I've understood that I have to do some homework
and that this bug can be closed. Thanks Jnhtn and Araraloren for your help
Regards,
Marcel
After some discussion I've understood that I have to do some homework
and that this bug can be closed. Thanks Jnhtn and Araraloren for your help
Regards,
Marcel
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131501]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131501 >
There were some fixes[^1] to prevent these ops from leaking thunks, and it
looks like the
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131502]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131502 >
The warning lies; this use isn't useless:
m: -> +@foo { say @foo.head.(41) }(* == 4
Oops. Long day. I meant WhateverCode is passed, not Junction.
Oops. Long day. I meant WhateverCode is passed, not Junction.
# New Ticket Created by rightfold
# Please include the string: [perl #131503]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131503 >
'-'.IO behaves as $*IN in some cases, like expected, but crashes with
slurp. '-'.IO.spurt w
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131504]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131504 >
I assumed the .&foo form was just a nicer way of writing foo($_), however they
differ in
For further providing you with informations about how to reproduce this NYI
bug, I've attached a perl script, that you can test perl6 with.
#!/usr/bin/perl6
my $i = 0;
itr:
$i++;
goto itr if ($i < 10);
say $i; #shall output 10
The attached script below, is meant for a Perl5 goto support, works fine -
which means that Perl6 has missed a feature from Perl5.
#!/usr/bin/perl
my $i = 0;
itr:
$i++;
print "$i\n";
goto itr if ($i < 10);
print "$i\n"; #shall output 10
# New Ticket Created by Richard Hainsworth
# Please include the string: [perl #131481]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131481 >
Here is a copy of my session. No perl6-debug.
All the documentation implies I shou
On Thu, 01 Jun 2017 22:25:55 -0700, rnhainswo...@gmail.com wrote:
> Here is a copy of my session. No perl6-debug.
>
> All the documentation implies I should have the executable. I'm running
> Ubuntu 16.04
Which documentation, out of curiosity? rakudobrew is mostly for core hackers,
not end user
On Thu, 01 Jun 2017 22:25:55 -0700, rnhainswo...@gmail.com wrote:
> Here is a copy of my session. No perl6-debug.
>
> All the documentation implies I should have the executable. I'm running
> Ubuntu 16.04
Which documentation, out of curiosity? rakudobrew is mostly for core hackers,
not end user
I would argue that perl6-debug shouldn't exist; if you are debugging, you
pretty much need to know the specific backend that's involved. Which is
likely why rakudobrew killed the generic one (the directory listing, while
mangled, *did* show perl6-debug-m).
On Sun, Jun 4, 2017 at 2:12 AM, Zoffix Zn
I would argue that perl6-debug shouldn't exist; if you are debugging, you
pretty much need to know the specific backend that's involved. Which is
likely why rakudobrew killed the generic one (the directory listing, while
mangled, *did* show perl6-debug-m).
On Sun, Jun 4, 2017 at 2:12 AM, Zoffix Zn
On Sat, 03 Jun 2017 12:47:03 -0700, rightf...@gmail.com wrote:
> '-'.IO behaves as $*IN in some cases, like expected, but crashes with
> slurp. '-'.IO.spurt works as expected; writing to $*OUT. It appears also
> that '-'.IO is not very well tested in roast, and it is not documented
> in the API
On Sat, 03 Jun 2017 12:47:03 -0700, rightf...@gmail.com wrote:
> '-'.IO behaves as $*IN in some cases, like expected, but crashes with
> slurp. '-'.IO.spurt works as expected; writing to $*OUT. It appears also
> that '-'.IO is not very well tested in roast, and it is not documented
> in the API
On Fri, 02 Jun 2017 09:53:58 -0700, kai...@protonmail.com wrote:
> For further providing you with informations about how to reproduce this NYI
> bug
Thank you for the report. It *is* known that goto is not yet implemented.
That's what the error message is trying to tell you.
> which means that P
On Fri, 02 Jun 2017 09:53:58 -0700, kai...@protonmail.com wrote:
> For further providing you with informations about how to reproduce this NYI
> bug
Thank you for the report. It *is* known that goto is not yet implemented.
That's what the error message is trying to tell you.
> which means that P
I think that runs perl6 -c, right?
Then no, I did not mean that.
I mean a tool for static analysis like Perl::Critic in Perl 5 that
would point out potential bugs,
or recommend better practices.
I've added a very naive implementation of checking for "use v6;"
https://github.com/Bailador/Bailador/b
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131505]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131505 >
(found in discussion in https://rt.perl.org/Ticket/Display.html?id=131493 )
We have some
On Sat, 03 Jun 2017 07:52:09 -0700, mt1...@gmail.com wrote:
> this bug can be closed
OK. Closing.
On Sat, 03 Jun 2017 02:36:12 -0700, alex.jakime...@gmail.com wrote:
> Well,
>
> say IntStr ~~ Str # True
>
> In other words, IntStr *is* a Str.
>
> What I find interesting, however, is this differ
On Sat, 03 Jun 2017 07:52:09 -0700, mt1...@gmail.com wrote:
> this bug can be closed
OK. Closing.
On Sat, 03 Jun 2017 02:36:12 -0700, alex.jakime...@gmail.com wrote:
> Well,
>
> say IntStr ~~ Str # True
>
> In other words, IntStr *is* a Str.
>
> What I find interesting, however, is this differ
On Sat, 03 Jun 2017 06:24:02 -0700, cookbook_...@yahoo.co.jp wrote:
> See the following codes and results:
>
> $ perl6 -e 'class A { multi method f(:$vert!, Code :&c = {;}){}; multi
> method f(:$func!, Code :&c = {;}){}; }; my $a = A.new;
> $a.f(:func(10));'
> Cannot resolve caller f(A: :func(Int)
On Sat, 03 Jun 2017 06:24:02 -0700, cookbook_...@yahoo.co.jp wrote:
> See the following codes and results:
>
> $ perl6 -e 'class A { multi method f(:$vert!, Code :&c = {;}){}; multi
> method f(:$func!, Code :&c = {;}){}; }; my $a = A.new;
> $a.f(:func(10));'
> Cannot resolve caller f(A: :func(Int)
36 matches
Mail list logo
