The issue doesn't seem to be the underscore, because I get the same result even
when converting the underscore into a letter ('b'):
$ cat gentb.p6
grammar G0 {
token TOP {|.*}
regex rport { }
rule ruport { }
#token type {+}
token type {+}
}
grammar G1 {
On Mon, Sep 11, 2017 at 09:48:01AM -0700, Dan Zwell wrote:
>
> `|` matches the longest input:
> > 'ab' ~~ / ^:ratchet [ . | .. ] $ /
> ｢ab｣
>
> If the regex contains empty code blocks, backtracking fails:
> > 'ab' ~~ / ^:ratchet [ {}. | {}.. ] $ /
> Nil
Isn't the whole point of :ratchet to turn
On Wed, Jul 05, 2017 at 06:10:42PM -0700, Will Coleda via RT wrote:
> On Wed, 05 Jul 2017 09:16:44 -0700, tbrowder wrote:
> > Given this invocation for a new installation of rakudo:
> >
> > perl Configure.pl --backend=moar --gen-moar --prefix=/some/dir
> >
> > /some/dir needs to exist and belo
On Sat, Sep 24, 2016 at 07:37:52AM +, Lloyd Fournier wrote:
> I think this is because .WHAT is a special case. It's not really a method
> which is what you need to make *.method work. *.WHAT will always return
> (Whatever) immediately.
You're correct that .WHAT is a special case. From S12, "I
On Sat, Jul 09, 2016 at 05:19:49AM -0700, Itsuki Toyota wrote:
> See the following results
>
> $ perl6 -e 'say -1 ** -0.1'
> -1
> $ perl6 -e 'say reduce * ** *, -1, (-0.1)'
> NaN
This is not a bug in "reduce" itself. Exponentiation has higher
precedence than unary minus, so the first expression
Added tests in roast/S03-operators/set.t, marking ticket resolved.
Pm
S05:792 mentions this case explicitly:
^^ always matches the beginning of the string and after
any \n that is not the final character in the string.
So, rakudo is performing exactly as specced.
I suspect the reason behind the spec is so that slurped \n-terminated
files (i.e., the vast m
The wikibooks example is wrong, Rakudo is correct here.
(To return the number of elements, use prefix:<+>, not the $-
contextualizer.)
Actually, that whole section in wikibooks seems to be a little "off"...
"@()" doesn't mean "convert to array", for example.
Closing ticket.
Pm
> So either STORE_AT_KEY for typed hashes should stringify objects
>silently if the keytype is Str, like untyped hashes do. Or untyped
>hashes should *not* automatically stringify objects.
Untyped hashes are {Str(Any)} -- see S09:1187:
The standard Hash:
my %hash;
is real
I'm wondering if this ticket can be marked "resolved" -- see
https://github.com/parrot/parrot/issues/365 .
The gist of #365 seems to be that parrot.h is no longer considered an
internal Parrot header file... but I'm not sure I'm reading it
correctly.
In particular, the parrot.h file itself n
On Sat May 25 21:13:26 2013, coke wrote:
> 23:54 < [Coke]> r: for 1..10 { my $a = 3; FIRST { say $a} }
> 23:54 <+camelia> rakudo 45ae2d: OUTPUT«(Any)»
>
> I would expect that to output "3".
>
Since the FIRST block is invoked before the assignment/initialization,
the output of "Any" seems corr
Now fixed in b1695cf:
pmichaud@kiwi:~/p6/rakudo$ cat x.p6
use MONKEY_TYPING;
augment class List {
proto method combinations(|) { * }
}
pmichaud@kiwi:~/p6/rakudo$ ./perl6 x.p6
pmichaud@kiwi:~/p6/rakudo$
Ticket closable with tests (hint: test that List.sink doesn't fail).
Pm
On Wed May 08 18:16:40 2013, grond...@yahoo.fr wrote:
> This is perl6 version 2013.04-55-gfe70494 built on parrot 5.2.0
> revision RELEASE_5_2_0
>
>
> use MONKEY_TYPING;
> augment class List { proto method combinations(|) {*} }
>
>
> Cannot look up attributes in a type object
It works for me i
Resolved via a change to S12, see
https://github.com/perl6/specs/commit/bff62668057bf3f87a6f80f33d088d47a1d
4eda2 .
Pm
Now fixed in 4741028:
pmichaud@kiwi:~/p6/rakudo$ cat g.pl
grammar G {
token TOP { +% }
token letter{<[a..z]>}
token sep{\,}
}
say G.parse("a,b,c,d").caps.map({$_.value});
pmichaud@kiwi:~/p6/rakudo$ ./perl6 g.pl
a , b , c , d
pmichaud@ki
On Thu, Feb 21, 2013 at 09:07:44AM -0800, Ricardo SIGNES wrote:
> This program never terminates:
>
> use v6;
>
> my @a = << >>;
> while (my @c = splice @a, 0, 3) {
> say "one more";
> }
After each splice, @c ends up being @(Any, Any, Any). I'm not
sure if this is correct; I can see
After thinking about this a bit, I'm inclined to disagree with the
original ticket.
my %h = 'foo' => [1,2,3], 'bar' => [4,5,6];
If %h{*} is analogous to @array[*], then it returns a list (slice) of
all of the elements of %h. The .[1] should then return the second
element of this slice, wh
Now fixed in 690d774; needs spectests to close ticket.
Thanks!
Pm
I suspect this bug may be related to #112716
(https://rt.perl.org/rt3/Ticket/Display.html?id=112716); the .map()
operation (which 'for' uses) tends to be a bit too eager in evaluating
its invocant list.
I've taken both bugs and will work on a fix shortly.
Pm
Now fixed in 0ed00f0 probably needs spectests to close ticket.
Thanks!
Pm
Now fixed in 7eae9b2:
pmichaud@kiwi:~/p6/rakudo$ ./perl6
> say ([|] 1..5).perl
any(1, 2, 3, 4, 5)
Ticket can be closed with appropriate spectests.
Pm
Now fixed in 84f4fd4:
> class ABC { our sub xyz() { 'xyz' } }; say ABC::.WHAT
Stash()
This ticket can be closed with sufficient spectests.
Pm
Now fixed in 2c9f46f. Needs spectests to close ticket.
Thanks,
Pm
On Tue Apr 03 01:24:47 2012, moritz wrote:
> 10:23 < timotimo> r: say "foo"[1..*]
> 10:23 <+p6eval> rakudo 8ead1e: OUTPUT«Method 'gimme' not found for
> invocant of
> class 'Str' in method postcircumfix:<[ ]> at
> src/gen/CORE.setting:1147 in block at
>
Now fixed in b1acd74. Needs spectest coverage to close ticket.
Thanks!
Pm
Now fixed in 69920db585.
> say &infix:<~>.arity
0
> say &infix:<~>.count
Inf
> say .reduce(&infix:<~>)
abcd
Ticket can be closed when we have appropriate spectests.
Thanks!
Pm
The speed of Array vs. Hash element access is partially addressed by
commit c10792f8. Before this commit, each Array element access via
.at_pos($pos) resulted in an expensive call to self.exists($pos) for
each access, whereas Hash element accesses via .at_key($key) were
able to use nqp::exists
> It would be helpful if someone (not necessarily the original poster)
> provided a recipe to build a perl6 without ICU so this bug can be
tested
> against a recent version.
The following should work:
perl Configure.pl --gen-parrot --parrot-option="--without-icu"
Pm
Now fixed in f9d94fe. There were already todo'd tests for this bug in
spectests, they're now un-todo'd and marked with this ticket number.
Thanks for the report, closing ticket!
Pm
Now fixed in (nom) 5d26134. Need a spectest and then we can close this
ticket.
Pm
On Sun Aug 07 12:25:15 2011, ronaldxs wrote:
> Seems at least partially fixed in nom but still may be related
concerns
> like
>
> nom: my $m = '34' ~~ /+|+/; say $m.perl; say
> Nil.perl; my $x = $m // 4; say 'x is ', $x
> nom: OUTPUT«()Nilx is »
>
> See http://irclog.perlgeek.de/perl6/2011-
Now fixed in 5ce8fcf:
> sub f { 1, 2, 4 }; .say for f.item
1 2 4
> sub f { 1, 2, 4 }; .say for $(f)
1 2 4
However, the fix exposes a problem with either .trans or trans.t, so
this ticket isn't quite closable yet. (And we need a spectest for it.)
Pm
On Sat Sep 18 10:55:52 2010, moritz wrote:
> Basic tests added to S03-operators/short-circuit.t.
>
> 19:52 < moritz_> rakudo: my $x; $x &&= 5; say $x
> 19:52 <+p6eval> rakudo a204ba: OUTPUT«5»
> 19:52 < moritz_> somebody please confirm that this is wrong
> ...
> 19:53 < jnthn> moritz_: Looks wron
I'm fairly certain that Rakudo's current behavior (returning a Failure
for indexes other than zero) is correct here. Switching "fail" to "die"
is definitely not correct.
I'm declaring this ticket "fixed" and can be resolved when we have
spectests verifying that the non-zero indexes return a Failu
Now fixed in 760c734:
pmich...@plum:~/rakudo$ ./perl6
> print .chr for <233 186 166 233 171 152>;
麦é«>
The TT #1793 ticket turned out to be a non-bug; the problem was in
Rakudo's setup of $*IN, $*OUT, and $*ERR.
I'm not sure how the current test suite would be able to test this
particul
Now fixed in 2f18a49, tests added to t/spec/S03-operators/bit.t .
Resolving ticket, thanks!
Pm
Now fixed in fca2d3. There's already a spectest for the test, but I'm
unable to commit spectest changes at the moment so I'll leave the ticket
open for someone else to close.
I also fixed .{*} in this patch, it probably needs tests as well.
Pm
On Fri Aug 06 12:56:24 2010, moritz wrote:
> 21:53 < moritz_> rakudo: for .kv -> $k, $_ { .perl.say }
> 21:53 <+p6eval> rakudo 0e5edb: OUTPUT«01»
> 21:53 < moritz_> huh.
> 21:54 < moritz_> shouldn't that be "a", "b" ?
> 21:54 < moritz_> rakudo: for .kv -> $k, $v { $v.perl.say }
> 21:54 <+p6eval>
Now fixed in b627e33. Assigning to moritz for spectest verification.
Thanks!
Pm
Now working in 51cc37:
pmich...@plum:~/rakudo$ ./perl6 --target=PIR hello.p6 >hello.pir
pmich...@plum:~/rakudo$ parrot_install/bin/parrot -o hello.pbc hello.pir
pmich...@plum:~/rakudo$ parrot_install/bin/pbc_to_exe hello.pbc
cc -o hello.o -I/home/pmichaud/rakudo/parrot_install/include/2.6.0-devel
Now working in 51cc37:
pmich...@plum:~/rakudo$ ./perl6 --target=PIR hello.p6 >hello.pir
pmich...@plum:~/rakudo$ parrot_install/bin/parrot -o hello.pbc hello.pir
pmich...@plum:~/rakudo$ parrot_install/bin/pbc_to_exe hello.pbc
cc -o hello.o -I/home/pmichaud/rakudo/parrot_install/include/2.6.0-devel
> new error:
>
> > my $a = 'abc'; say $a[1];
> ===SORRY!===
> .[1] out of range for type Str()
>
I believe this is the correct behavior per the specification.
Pm
The spec changed to use $*VM, and Rakudo now implements that.
> say $*VM
/home/pmichaud/rakudo/parrot_install/bin
>
Pm
Now fixed in 9005478:
pmich...@plum:~/rakudo$ ./perl6
> say "b" ~~ /(.*)b/;
b
> say "ab" ~~ / (ab|a) b /;
ab
> grammar G { regex TOP { a }; regex foo { a* } }; say
?G.parse("aaa");
1
>
Pm
Now fixed in c18d372. Assigning to moritz++ for spectest coverage.
Thanks!
Pm
On Mon Jun 28 04:49:23 2010, lemb...@wrkhors.com wrote:
> Using the June release:
>
> $ perl6 --version
> This compiler is built with the Parrot Compiler Toolkit, parrot
> revision 47640.
>
> Attempting to print some random numers via Bool.pick
> gives no output:
For a wide variety of reasons, R
Now fixed in current Rakudo, assigning to moritz for spectest coverage.
Pm
On Sun Jun 27 14:16:46 2010, pkailasa wrote:
> # this fails
> >> perl6 -e 'my @a = 0, 1, 2; for @a { if $_ { $_++ } }; say @a.perl'
> [0, 1, 2]
It now works in current Rakudo:
pmich...@plum:~/rakudo$ cat x
my @a = 0, 1, 2;
for @a { if $_ { $_++ } };
say @a.perl;
pmich...@plum:
Now fixed in a579f8e. Closing ticket.
Pm
Now fixed in 841262f. Assigning to moritz++ for test verification to
close ticket.
Pm
Now fixed in 06723b4... assigning to moritz++ for test verification and
unfudging.
Pm
On Wed Jun 02 14:50:54 2010, david.gr...@telus.net wrote:
> Creating several regexes should return several different objects:
>
> say /@_[0]/, /@_[1]/, /@_[2]/ given
> _block27 _block35 _block43
>
>
> However, inside a loop, instead of different regexes, the final one
> gets repeated:
>
In the new master branch, self is no longer writable. I don't know if
we need a test for this ticket before closing it (I suspect we do).
Pm
An undeclared dynamic variable currently results in a failure;
attempting to assign to that failure produces the readonly message.
Perhaps assignment to a failure should throw its exception?
Pm
Now fixed in 12ea7b9:
> say (my $a eqv $a);
1
> say Mu eqv Mu
1
Need to verify we have tests for this.
Pm
Now fixed in 4ab4b8. Probably needs a test before we can resolve the
ticket.
Pm
Now fixed in c495888. Closing ticket.
Pm
Now fixed in fad9447. Need to verify existence of a spectest for this
and then the ticket can be closed.
Pm
Marking ticket as resolved, as Rakudo currently matches the specification.
Pm
Now fixed in 3a274d9. We probably need a spectest in order to close the
ticket.
Thanks!
Pm
Now fixed in f351f60:
$ cat x
class A {
has $.a is rw;
method add(A $b) { $.a ~ $b.a }
}
multi sub infix:<+>(A $a, A $b) { $a.add($b) };
my A $a .= new(a=>'foo');
my A $b .= new(a=>'bar');
say $a.a ~ $b.a;
say $a + $b;
$ ./perl6 x
foobar
foobar
$
Assigning to moritz++ so that we can
On Sun Aug 09 14:56:24 2009, moritz wrote:
> It seems that the :foo[...] colonpair syntax doesn't set up the array
> sufficiently non-flattening:
Correct, Rakudo doesn't handle the non-paren colonpair syntaxes yet
(they were recently refactored in STD.pm and haven't caught up). This
ticket is rea
On Sat Jul 11 06:57:11 2009, richardh wrote:
> perl6
> > my @x=1,2,3,4; my @z; for @x { @z[+*] = $_ }; @z.perl.say
> [4]
> > my @x=1,2,3,4; my @z; for @x { @z...@z] = $_ }; @z.perl.say
> [1,2,3,4]
Now fixed in f48920, thanks!
$ ./perl6
> my @x = 1,2,3,4; my @z; for @x { @z[+*] = $_ }; @z.
On Wed Jul 29 05:30:51 2009, colo...@gmail.com wrote:
> According to http://perlcabal.org/syn/S03.html#Nesting_of_metaoperators
> +* should generate a closure which numifies. This does not work, as
>
> my $x = +*;
> isa_ok $x, Code, '+* is of type Code';
>
> fails, as do attempts to use
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #68142]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68142 >
S09:1043 says that junctions passed as components of a slurpy
array or hash do not
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #68140]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68140 >
01:38 my $out = open "02.pl", :w or die "Unable to open 02.pl: $!\n";
01:39 Wor
> Yes, it's still there. It's the 'cd' at the beginning of this line:
>
> cd $(PMC_DIR) && $(CC) -c $(CINCLUDES) $(CFLAGS) *.c
>
> If memory serves, parrot doesn't change directories like that.
> Instead, it sets
> the output location directly, with something like
>
> $(CC) -c $(CIN
On Tue Jul 28 19:03:45 2009, wayland wrote:
> Attached patch is updated according to pmichauds comments on IRC
recently.
Patch applied to ins2 branch in ce21ff.
As soon as we get the Sun compiler issues resolved (RT #66560) I think
we may be able to merge to trunk and close this ticket.
Pm
On Fri Jun 12 13:42:59 2009, doughera wrote:
> Trying a build with the rakudo "ins" branch today on OpenSolaris/x86
>with
> Sun's compiler, I hit the following error:
>
> [...]
> "./src/pmc/p6invocation.pmc", line 22: cannot find include file:
>"pmc_perl6multisub.h"
> cc: acomp failed for
On Sat Jun 13 19:07:16 2009, ing...@exherbo.org wrote:
> This is using Rakudo's inc branch, building against parrot trunk,
>r39541.
>
> Seems to work fine up until it tries to build the perl6 executable.
> When building the perl6 executable, $(CINCLUDES) isn't passed to the
>compiler,
> as
On Fri Jun 12 11:36:31 2009, doughera wrote:
> In the 'ins' branch, build/Makefile.in looks like it's heading down the
> same wrong road as parrot. See parrot's TT #700 for more details and a
> patch for parrot. I'd suggest a similar approach for rakudo.
>
> The problem is that while MS forbid
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #67866]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67866 >
19:37 rakudo: say any("foo","bar").WHAT
19:37 rakudo dd5767: OUTPUT«Null PMC ac
On Sun Mar 15 08:36:42 2009, masak wrote:
> rakudo: sub foo { return }; say foo.WHAT; say ?(foo ~~ Nil)
> rakudo 5b1ff9: OUTPUT«Nil0»
> * masak submits
>
> Expected behavior: a "Nil" and a 1. Or an explanation about why a
> value shouldn't smartmatch successfully against its own type.
Note th
I've changed this ticket to indicate that it's waiting on spec
clarification as to the exact meaning of in regexes.
Pm
On Sun Jun 21 10:44:43 2009, moritz wrote:
> iterating over $*VM.kv shows more than one key:
>
> $ perl6 -e 'my $keys = 0; for %*VM.kv -> $k, $v { $keys++}; say $keys'
> 141
>
> Somehow the inner hash is flattened. Using a normal hash I couldn't
> reproduce
> this behaviour.
Now fixed in 6c6299f
On Sun Jun 21 23:57:17 2009, amoc wrote:
> : bash$ perl6
> : > 1 ?? 1,2 !! 3,4
> : Ternary error
> : bash$
>
> this is not wrong as infix:<,> has looser precedence than the ternary
> operator( ?? !! )
> but when ternary error occurs, the program emits the error and dies.
>
> should provide the pr
On Tue Jun 30 18:47:59 2009, KyleHa wrote:
> I've written a test for this in S12-methods/what.t in r27345.
Thanks! Closing ticket!
Pm
Now fixed in ee1fd13:
$ ./perl6
> say &infix:<+>.WHAT
Multi()
Assigning to moritz++ for spectest coverage, if needed.
Pm
On Sun Oct 26 12:27:26 2008, masak wrote:
> Rakudo r32151 contains a bug which makes it "read" a nonexistent blank
> line at the end of files.
>
> $ wc README | awk '{ print $1 }'
> 102
>
> $ =$*IN; }; say $l'
> 103
IO.pod:1207 claims that "IO.eof" is gone, to be replaced with
C. But I can't s
On Fri Jun 26 07:56:40 2009, masak wrote:
> rakudo: my $a = :x[]
> rakudo 6c43f9: OUTPUT«Null PMC access in find_method() [...]
> * masak submits rakuodbug
> rakudo: :x[]
> rakudo 6c43f9: OUTPUT«Null PMC access in find_method() [...]
What should $a contain in the above case? I.e., what's the
The infix: operator has now been added in Rakudo a4978b9, with a
test added to t/spec/S03-operator/misc.t in r27322.
Closing ticket,
Pm
Rakudo 95a2c4f now gives a more useful error message when returning the
failure for not finding a given substring:
pmich...@orange:~/rakudo$ ./perl6
> say index "abcd", "x"
Substring 'x' not found in 'abcd'
Closing ticket, thanks!
Pm
Now fixed in e0a9d86, and we now have several operators being defined in
the setting (along with tests using those operators).
Closing ticket, thanks!
Pm
On Mon Jun 29 00:36:42 2009, fernandocor...@gmail.com wrote:
> implemented:
> - "not" "Object"'s method
> - "sign" "Num"'s method
>
> Thats my first time to send a patch, I don't know if its OK, but I really
> want to help.
Thank you for the patches! However, they may need some refactoring (or
This is a Parrot bug. Recently the Parrot team have been working to
clean up memory leaks in context handling, and as a result we're
starting to see "double free" errors on exit again. Running Rakudo with
Parrot's -G flag avoids the backtrace.
I'll leave this ticket open for now but mark it as "
On Tue Jun 16 10:14:11 2009, richardh wrote:
> my @a=1,2,3,4; my @b=9,8,7,1; say (@a minmax @b).perl
While rakudo doesn't implement infix: yet, the operator is
constrained to having two elements on either side, so the above code
wouldn't work anyway.
It would be good to have some tests for infix:
This was caused by a bug in Parrot; the problem in Parrot seems to have
been resolved and now EOF appears to work again.
Closing ticket, thanks!
Pm
I don't have any idea where the problem might be; since the Rakudo team
doesn't build the packages you installed I'm not quite sure where to
being troubleshooting.
I suggest contacting the packager who put together the binaries; try
with the latest Rakudo release; or see if you can build Rakudo fr
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #66790]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=66790 >
The following code demonstrates that MultiSub and Perl6MultiSub
do not stringify t
At the moment string ranges are only defined for certain subsets of
Unicode. See the description under "Autoincrement precedence" in
Synopsis 3.
More to the point, if you want to cycle through a range of codepoints,
you probably want:
map { .chr }, 44032..45208;
I agree that the string form
On Mon Jun 08 06:51:53 2009, masak wrote:
> Rakudo doesn't support '=begin SUMMARY' Pod syntax!?
[...]
> rakudo: role A;=begin SUMMARYThis be a summary.=end
> SUMMARYsay "OH HAI"
> rakudo 5f70a6: OUTPUT«Unable to parse role definition at line
> 2, near ";\n=begin S" [...]
> ah. there we go.
On Sun Jun 07 00:57:34 2009, patmar19 wrote:
> When I try pugs or perl6 I get strange results whith Str methods :
>
> pugs -e 'say "1234é".chars' => 5
> perl6 -e 'say "1234é".chars' => 6
>
> pugs -e 'say "1234é".bytes' => 6
> perl6 -e 'say "1234é".bytes' => 8
>
> pugs -e 'say "1234é".graphs' =>
Test now added to S05-grammar/std.t, closing ticket.
Pm
Now added in 056847f. Please add a test to t/spec so we can close this
ticket. :-)
Pm
Now fixed in 9e2b9ad:
$ cat 66280
for 1,3 -> $i {
for $i..4 -> $j { say "$j,$i" };
$i.say;
}
$ ./perl6 66280
1,1
2,1
3,1
4,1
1
3,3
4,3
3
$
Test added to range.t. Closing ticket, thanks!
Pm
On Wed Jun 03 06:08:46 2009, haakonsk wrote:
> This doesn't work:
> grammar A { rule TOP { 'a' ' b' {*} } }; my $m = A.parse('a b'); say $/;
> Result: Empty string
> Expected result: "a b"
Rakudo is correct here.
Whitespace in rules is metasyntactic -- it gets replaced by <.ws>.
So, the above r
The current version of Rakudo (after Jonathan's merge) now reports:
$ cat 66182
my $x;
[$x.WHAT, $x.HOW, $x]>>.say;
$ ./perl6 66182
Failure()
Method 'say' not found for invocant of class 'P6metaclass'
$
I don't know if this is more along the lines of what you were lo
This code appears to be working for me:
$ cat 65412
class A {
has $!rx;
method do { $!rx = / xyz / }
}
A.new.do
$ ./perl6 65412
$
I suspect the problem is really with the evalbot attempting to evaluate
the returned regex in boolean context after the progr
This is now working properly in c907d37 ... assigning ticket for
spectest verification, and then it can be closed.
Thanks!
Pm
Rakudo now gives a much more useful error message for the case where
make() cannot set a result object:
$ cat 63800
grammar G {
regex TOP { 'a' {*} }
}
class GA {
method TOP($m) { make GA.new }
}
G.parse('a', :action(GA.new));
$ ./perl6 63800
make
1 - 100 of 418 matches
Mail list logo
