On Wed, 20 Jul 2016 08:32:12 -0700, c...@zoffix.com wrote:
> I was able to golf it a bit further (still present in Rakudo 58dc8c).
> Removing >> or changing first-match || to longest-match | no longer
> shows the bug:
>
> m: "bc" ~~ /||@() >>/ or say "Failed"
> rakudo-moar 58dc8c: OUTPUT«Failed»
It affects `|` array interpolation as well:
➜ say "ab" ~~ / < ab a > b /;# 「ab」
➜ say "ab" ~~ / @() b /; # Nil
➜ say "ab" ~~ / |@() b /; # Nil
On Wed, 22 Feb 2017 05:45:54 -0800, c...@zoffix.com wrote:
> I notice the first thing[^1] our `use` pragma looks for when it gets a
> version is `v5` and tries to load `Perl 5` module:
>
> That doesn't appear to be a thing any more. Should that conditional be
> tossed from the grammar?
>
> m: use
On Wed, 22 Feb 2017 05:45:54 -0800, c...@zoffix.com wrote:
> I notice the first thing[^1] our `use` pragma looks for when it gets a
> version is `v5` and tries to load `Perl 5` module:
>
> That doesn't appear to be a thing any more. Should that conditional be
> tossed from the grammar?
>
> m: use
On Sat, 31 Oct 2015 15:23:12 -0700, coke wrote:
> --
> Will "Coke" Coleda
Pretty sure it's now implemented as we needed it during Proc refactor.
On Sat, 31 Oct 2015 15:23:12 -0700, coke wrote:
> --
> Will "Coke" Coleda
Pretty sure it's now implemented as we needed it during Proc refactor.
# New Ticket Created by
# Please include the string: [perl #132236]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132236 >
Hi,
Given a module (Suptest.pm):
my package EXPORTHOW {
class SUPERSEDE::class is Metamod
This was fixed ages ago which can be verified with
c: releases my $f = open("/tmp/dasdasdasdastest.txt", :r, :w);
$f.write("hello".encode); $f.seek(0); say $f.read(5).decode
also, tests are present in t/spec/S32-io/open.t. Setting to resolved.
On Fri, 06 Oct 2017 19:32:17 -0700, b...@abrij.org wrote:
> On Fri, 15 Jan 2016 10:24:16 -0800, c...@zoffix.com wrote:
> > The slip (|) before a range has higher precedence and it interprets
> > the starting point of the range as a single-item list. This leads to
> > two types of bugs, and both sit
On Sat, 07 Oct 2017 06:04:53 -0700, c...@zoffix.com wrote:
>
> Pretty sure it's now implemented as we needed it during Proc refactor.
Yes, Proc::Async works on the jvm backend now. Resolving this issue.
On Thu, 01 Jun 2017 16:07:41 -0700, ju...@tnx.nl wrote:
> code:
>
> class Command { method Str { "<$.^name>" } }
> # or even just:
> class Command { method Str { $.^name } }
>
> gives:
>
> Unsupported use of $. variable; in Perl 6 please use the .kv method on
> e.g. .lines
>
> workaround:
>
>
AlexDaniel: FWIW jnthn++ said we'll likely make ». autothread only is
pure routines, so no shuffling is really needed
On 2017-01-02 11:31:47, alex.jakime...@gmail.com wrote:
> Code:
> ».say
>
> Result (2015.07):
> d
> b
> c
> a
>
> Result (HEAD):
> a
> b
> c
> d
>
>
> The idea was that the order
Zoffix: so ».say should not be discouraged? Interesting
AlexDaniel_: well, that's based on an off-hand comment in IRC chat.
Not a final design descision :)
On 2017-10-07 09:32:43, alex.jakime...@gmail.com wrote:
> AlexDaniel: FWIW jnthn++ said we'll likely make ». autothread
> only is
> pure ro
» is supposed to be an explicit promise that you don't care about
order, and there are lots of places that are not marked pure that are
nevertheless effectively pure
On 2017-10-07 09:34:59, alex.jakime...@gmail.com wrote:
> Zoffix: so ».say should not be discouraged?
> Interesting
> AlexDaniel_
PR was merged, tests needed.
On 2017-10-06 19:40:44, alex.jakime...@gmail.com wrote:
> See this pull request: https://github.com/rakudo/rakudo/pull/1183
>
> Unfortunately not all of the things are covered. For example:
>
> perl6 -e 'my $x = q:to/foo/;
> blah
> '
> ===SORRY!=== Error while compilin
Ah, sorry. Even though some tests are needed, this ticket is still not fully
resolved. I'll try to split it right now.
On 2017-10-07 09:40:03, alex.jakime...@gmail.com wrote:
> PR was merged, tests needed.
>
> On 2017-10-06 19:40:44, alex.jakime...@gmail.com wrote:
> > See this pull request: https
Thanks, indeed.
Bisectable points to
https://github.com/rakudo/rakudo/commit/2574f8835f7e1342e848c0135fbed6319d55eb0e
On 2017-10-07 06:52:35, j...@gellyfish.co.uk wrote:
> Hi,
> Given a module (Suptest.pm):
>
> my package EXPORTHOW {
> class SUPERSEDE::class is Metamodel::ClassHOW {
> has $.foo;
Some discussion: https://irclog.perlgeek.de/perl6/2017-10-07#i_15271146
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132238]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132238 >
See https://rt.perl.org/Ticket/Display.html?id=125641 for the history
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132237]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132237 >
See https://rt.perl.org/Ticket/Display.html?id=125641 for the history
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132239]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132239 >
See https://rt.perl.org/Ticket/Display.html?id=125641 for the history
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132240]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132240 >
See https://rt.perl.org/Ticket/Display.html?id=125641 for the history
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132241]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132241 >
See https://rt.perl.org/Ticket/Display.html?id=125641 for the history
OK. There are 5 new tickets for all other issues. In this particular ticket
let's talk about (), [], "", etc. Basically, anything that currently says
“corresponding starter” (word “starter” instead of the actual starter). It
should really print the actual starter, but for now it's a good way to fig
FWIW, here was my attempt to resolve this issue:
diff --git a/src/Perl6/Grammar.nqp b/src/Perl6/Grammar.nqp
index 13c09feb9..09b05bac7 100644
--- a/src/Perl6/Grammar.nqp
+++ b/src/Perl6/Grammar.nqp
@@ -3553,6 +3553,9 @@ grammar Perl6::Grammar is HLL::Grammar does STD {
|
]
| $ >
<.typed_sorry: '
Should be fixed in https://github.com/rakudo/rakudo/commit/5747bc7121
Testneeded. Slightly relevant tests here:
https://github.com/perl6/roast/commit/34577134e0
Should be fixed in https://github.com/rakudo/rakudo/commit/5747bc7121
Testneeded. Slightly relevant tests here:
https://github.com/perl6/roast/commit/34577134e0
On 2017-10-06 21:01:48, alex.jakime...@gmail.com wrote:
> This one is a bit harder than it seems.
>
> So here is what throws:
>
https://
I merged the PR. Thank you for you patience.
「testneeded」
See
https://github.com/rakudo/rakudo/commit/c7a82d451d6506bda9422813fe72974575e473df
You can see some code examples here:
https://github.com/rakudo/rakudo/pull/565#issuecomment-334965048
Maybe these can be turned into tests easily.
On 20
“Couldn't the confusing wording be fixed without additional information?”
Yes. But how? We can't *remove* this hint because sometimes it is super useful.
On 2017-10-06 11:13:34, sml...@gmail.com wrote:
> On Wed, 04 Oct 2017 22:10:22 -0700, alex.jakime...@gmail.com wrote:
> > To produce an error m
Is it possible to signal to the error handler that it is talking about a
value somewhere instead of the program source, at least? Even if you can't
reasonably say what value where?
On Sat, Oct 7, 2017 at 5:18 PM, Aleks-Daniel Jakimenko-Aleksejev via RT <
perl6-bugs-follo...@perl.org> wrote:
> “Co
Is it possible to signal to the error handler that it is talking about a
value somewhere instead of the program source, at least? Even if you can't
reasonably say what value where?
On Sat, Oct 7, 2017 at 5:18 PM, Aleks-Daniel Jakimenko-Aleksejev via RT <
perl6-bugs-follo...@perl.org> wrote:
> “Co
Yeah.
On 2017-10-02 22:10:56, alex.jakime...@gmail.com wrote:
> Actually, this is a dup of
> https://rt.perl.org/Ticket/Display.html?id=128804 ,
> and I think it's now resolved.
>
> On 2015-12-30 12:39:37, alex.jakime...@gmail.com wrote:
> > Code:
> > say :5<1.I>
> >
> > Result:
> > ===SORRY!=== E
This seems to have been fixed with commit
https://github.com/rakudo/rakudo/commit/d1c2e7649884a48a4733666c1425d8dcb4918120.
There were tests added at the same time, i.e.
https://github.com/perl6/roast/commit/e797f925515ac93f814fa34b6eef291a05fe8a46
but I'm unsure if those tests cover this RT. I
This was resolved in these commits:
*
https://github.com/rakudo/rakudo/commit/ac97a4016196c1fb5c39365dfbe8980574fb929b
*
https://github.com/rakudo/rakudo/commit/64b001a1464bf618fa4c0eed984e240fcf8b772b
「testneeded」
Please try to cover various variants in tests, like:
(--> Bool Int $x, Int $y)
(--
FWIW I agree about the “debug” mode.
That said, it isn't just a nice-to-have. This is something that can make people
mention Perl 6 when discussing the most amazing features of modern programming
languages… much like people mention grammars today :)
On 2016-01-17 04:07:19, jn...@jnthn.net wrote:
>
Actually, it's not about the error message. The whole thing can be golfed to
this:
enum Foo (:Bar(1), :Baz(True))
And the error happens because:
Code:
use nqp;
say so nqp::istype(True, Int);
nqp::rebless(True, Int)
Result:
True
Incompatible MROs in P6opaque rebless for types Bool and Int
in blo
Zoffix++ pointed out that there is a problem with IntStr also:
Code:
enum Foo (:Bar(1), :Baz(<42>))
Result:
===SORRY!===
Incompatible MROs in P6opaque rebless for types IntStr and Foo
On 2017-10-07 17:16:30, alex.jakime...@gmail.com wrote:
> Actually, it's not about the error message. The whole
FWIW to add it one will need to hack this part:
https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e4555ded27cba91/src/Perl6/Actions.nqp#L7999-L8055
See the implementation for S/// for more inspiration:
https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e4555ded27cba91/src/
FWIW to add it one will need to hack this part:
https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e4555ded27cba91/src/Perl6/Actions.nqp#L7999-L8055
See the implementation for S/// for more inspiration:
https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e4555ded27cba91/src/
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 this part:
>
https://github.com/rakudo/rakudo/blob/de0533c4d4c9f425ce22432a8e45
Basically, this would need to throw X::Syntax::KeywordAsFunction, but it blows
up when trying to look up $test so that's rather unfortunate. Pretty sure we
can do something about it but maybe it's not a one-line fix.
On 2016-04-07 16:29:37, alex.jakime...@gmail.com wrote:
> Code:
> my($test) = 42
On Sun, 17 Sep 2017 15:17:47 -0700, alex.jakime...@gmail.com wrote:
> Plain-wrongs and WHATs print different results today. Bisectable
> points at
> https://github.com/rakudo/rakudo/commit/242baf256a210f1cb643cb6324916dbc76184c9f
>
> I think we now only need tests for this ticket.
>
> On 2015-06-
On Sun, 17 Sep 2017 15:17:47 -0700, alex.jakime...@gmail.com wrote:
> Plain-wrongs and WHATs print different results today. Bisectable
> points at
> https://github.com/rakudo/rakudo/commit/242baf256a210f1cb643cb6324916dbc76184c9f
>
> I think we now only need tests for this ticket.
>
> On 2015-06-
# New Ticket Created by Itsuki Toyota
# Please include the string: [perl #132242]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132242 >
See the following result:
$ perl6 -e 'my $proc = Proc::Async.new("yes"); $proc.stdout.h
On Sat, Oct 7, 2017 at 10:21 PM, Itsuki Toyota wrote:
> See the following result:
>
> $ perl6 -e 'my $proc = Proc::Async.new("yes");
> $proc.stdout.head(1).tap(&say); await $proc.start;'
>
> y
> y
> y
> y
> y
> y
> y
> y
> ...
>
>
> I think tap(&say) should output just a 'y' char and completes it
On Sat, Oct 7, 2017 at 10:21 PM, Itsuki Toyota wrote:
> See the following result:
>
> $ perl6 -e 'my $proc = Proc::Async.new("yes");
> $proc.stdout.head(1).tap(&say); await $proc.start;'
>
> y
> y
> y
> y
> y
> y
> y
> y
> ...
>
>
> I think tap(&say) should output just a 'y' char and completes it
I created this doc issue: https://github.com/perl6/doc/issues/1591
On 2017-10-07 19:33:40, allber...@gmail.com wrote:
> On Sat, Oct 7, 2017 at 10:21 PM, Itsuki Toyota > wrote:
>
> > See the following result:
> >
> > $ perl6 -e 'my $proc = Proc::Async.new("yes");
> > $proc.stdout.head(1).tap(&say)
On Sat, 06 Jun 2015 20:24:32 -0700, r...@hoelz.ro wrote:
> Let's say I have an array where @array.end == $end. Using
> @array[0..$end] is about 20 times faster than @array[0..*]. I have
> attached an example script that demonstrates this.
Thanks for the report, however there's no issue with the
On Sat, 06 Jun 2015 20:24:32 -0700, r...@hoelz.ro wrote:
> Let's say I have an array where @array.end == $end. Using
> @array[0..$end] is about 20 times faster than @array[0..*]. I have
> attached an example script that demonstrates this.
Thanks for the report, however there's no issue with the
So-o. Zoffix insists that everything is correct here, and perhaps it is so.
That being said, I don't quite understand why it can't be done. Maybe somebody
else can take a look also. Here's my logic:
So if you have
@array[0...@array.end]
and
@array[0..*]
Would we get identical results from both
On Sat, 07 Oct 2017 22:19:46 -0700, alex.jakime...@gmail.com wrote:
> why can't it just pretend that * is @array.end?
Done now in https://github.com/rakudo/rakudo/commit/456358e3c3
On Sat, 07 Oct 2017 22:19:46 -0700, alex.jakime...@gmail.com wrote:
> why can't it just pretend that * is @array.end?
Done now in https://github.com/rakudo/rakudo/commit/456358e3c3
Tests were added in https://github.com/perl6/roast/pull/344/files
There are three fudges where it's unknown what the proper behaviour should be
(overflow or switch to Int?).
Someone Who Knows should review them and unfudge/correct.
Tests were added in https://github.com/perl6/roast/pull/344/files
There are three fudges where it's unknown what the proper behaviour should be
(overflow or switch to Int?).
Someone Who Knows should review them and unfudge/correct.
On Tue, 03 Oct 2017 17:52:39 -0700, c...@zoffix.com wrote:
> Perhaps it should throw when it was given trailing stuff after the
> relevant char?
>
> 00:49 dpk m: say unival("1\x[300]23")
> 00:49 camelia rakudo-moar 98fae3: OUTPUT: «1»
> 00:50 dpk that … seems like a potential securi
55 matches
Mail list logo