Erm, I'm very sorry. I closed the wrong ticket (and also hit the 'Update
Ticket' button twice).
I'm re-opening this ticket.
This fails now with a typed exception "X::Syntax::ArgFlattener".
$ perl6 -e 'say(|(|([4])))'
===SORRY!=== Error while compiling -e
Arg-flattening | is only valid in an argument list
at -e:1
--> say(|(|⏏([4])))
Please note that the first '|' is valid (argument list for 'say'):
$ perl6 -e 'say
I added tests for the output of the above examples of 'is_deeply' to
S24-testing/3-output.t with commit
https://github.com/perl6/roast/commit/5a9c4e27ab
The test file S24-testing/3-output.t is not yet in Rakudo's t/spectest.data,
therefore I'm leaving this ticket open.
All those evaluations look good to me now:
$ perl6 -e 's[ea] = "rea"; .say; .perl.say'
""
$ perl6 -e '$_ = "real"; s[ea] = "rea"; .say'
rreal
$ perl6-m -e '$_ = ""; s[] = "rea"'
===SORRY!=== Error while compiling -e
Null regex not allowed
at -e:1
--> $_ = ""; s[⏏] = "rea"
I added tests for
nbrown++ added a test to S02-literals/heredocs.t with commit
https://github.com/perl6/roast/commit/9b7d709fd7.
I'm closing this ticket as 'resolved'.
This dies no with a typed exception X::TypeCheck
$ perl6-m -e 'my (Str $a) = 3'
Type check failed in assignment to '$a'; expected 'Str' but got 'Int'
in method STORE at src/gen/m-CORE.setting:9265
in block at -e:1
I added a test to S04-declarations/my.t with commit
https://github.com/perl6/
There was already a (skipped) test in S14-roles/parameterized-type.t. I
adjusted the test to use '@!children handles ' as
Mouq++ pointed out:
https://github.com/perl6/roast/commit/223db17d80
I'm closing this ticket as 'resolved'.
The first evaluation fails again (no method 'subst-mutate' nowadays), so I'm
re-opening this ticket.
$ perl6 -e 's[ea] = "rea";'
Method 'subst-mutate' not found for invocant of class 'Any'
in block at -e:1
We're back to "We could improve the error, but what should it say" (moritz,
2012) and
This works now and there is a passing test in S03-sequence/basic.t
$ perl6 -e 'say [] ... []'
$ perl6 -e 'say ([] ... []).perl'
([],)
I'm closing this ticket as 'resolved'.
This was fixed promptly. The code now dies with the right exception.
$ perl6 -e'my@x=^10;my@y=2..3;my@z=@y??@x[@y]:v!!@x'
===SORRY!=== Error while compiling -e
Precedence of :v is too loose to use inside ?? !!; please parenthesize
at -e:1
--> my@x=^10;my@y=2..3;my@z=@y??@x[@y]:v⏏!!@x
expec
This was fixed by TimToady++. The test is passing again.
I added two tests to S03-sequence/basic.t which should cover the underlying
problem (containers returned from the seq iterator were not respected):
https://github.com/perl6/roast/commit/2be443bf3f
I'm closing this ticket as 'resolved'.
As a status update: we're back at the original failures:
$ perl6 -e 'my $t = q[%foo% %bar% %foo% %baz%]; my %b = foo => 1, bar => 2, baz
=> 3; $t.=subst("%{.key}%", .value, :g) for %b.pairs; say $t'
Method 'key' not found for invocant of class 'Any'
in block at -e:1
$ perl6-m -e 'my %b = foo
This works now.
$ perl6-m -e 'my $handle = pipe("/usr/bin/false", :r); say $handle.close'
Proc::Status.new(exit => 1, pid => Any, signal => 0)
There are passing tests in S32-io/pipe.t.
I'm closing this ticket as 'resolved'.
This dies now with the same typed exception:
$ perl6 -e 'my $rx = "+"; "" ~~ /<$rx>/; say "alive"'
===SORRY!=== Error while compiling EVAL_0
Quantifier quantifies nothing
at EVAL_0:1
--> anon regex { +⏏}
But as masak pointed out, S05 says it should not die:
On Sat Dec 20 13:10:32 2014, masak
< jepeway> could somebody delete RT #124392? It's a dup from when I e-mailed
rakudobug@ w/o [BUG] in Subject: header
I'm going to add a link to RT #124393 and delete this ticket.
The segfault with MoarVM is fixed. The new error message seems LTA, though.
$ perl6-m -e 'next; CONTROL { }'
flatten requires a concrete string, but got null
in regex at ././CORE.setting.moarvm:1
in block at -e:1
This test actually works:
$ perl6 -e 'my $ok; constant λ = 42; $ok = λ == 42; say $ok'
True
I'm closing this ticket as 'resolved'.
These tests relied on 'try' catching a compile time error. I changed the tests
to use 'try { EVAL ...' and they are passing now:
https://github.com/perl6/roast/commit/f5deb5ca1f
I'm closing this ticket as 'resolved'.
These tests passed for the most part. I removed the fudging and fixed the last
test: https://github.com/perl6/roast/commit/692d7be0fc
As masak pointed out, that last test is not very specific. (But at least it's
not wrong.)
< bartolin> ^^ could someone review that commit, please? as in: was the
This works now. I unfudged the existing test and added a second test to
S03-operators/assign.t
with commit https://github.com/perl6/roast/commit/fdaa7dc62e
I'm closing this ticket as 'resolved'.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/b62c8ee446.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/b62c8ee446.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/629b80d6ee.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/629b80d6ee.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/88954b01cd.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/8e3489cff3
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/dc34eeacfd
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/e4252cd33a
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/6a71064e8d.
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/cac9919391
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/cac9919391
This test is actually passing. I unfudged the test with commit
https://github.com/perl6/roast/commit/aacaa5e9ab
This tests are actually passing. I unfudged the tests with commit
https://github.com/perl6/roast/commit/a5397a6a09
These tests are actually passing. I unfudged the tests with commit
https://github.com/perl6/roast/commit/c9e7946599
These tests are actually passing. I unfudged the tests with commit
https://github.com/perl6/roast/commit/c9e7946599
These tests are actually passing. I unfudged the tests with commit
https://github.com/perl6/roast/commit/c9e7946599
These tests relied on stringification for comparing signatures. I changed the
tests to use .perl and the tests are passing now:
https://github.com/perl6/roast/commit/2e6f3e1695
If there is a better way to compare those signatures, please improve the tests
or reopen the ticket.
It is possible to quote with \0 as delimiter. STD allows that as well.
I adjusted the test, which is passing now:
https://github.com/perl6/roast/commit/99a3eed0f0
I fixed these two tests for q:x and qq:x with commit
https://github.com/perl6/roast/commit/99a3eed0f0
This test is passing now, cmp. https://github.com/perl6/roast/commit/52cd1b67
On Sun May 10 05:38:00 2015, barto...@gmx.de wrote:
> There are failing (fudged) tests in S05-transliteration/with-closure.t
> because closures within .trans are sometimes executed too often.
>
> $ perl6 -e 'my $x = 0; say "aXbXcXd".trans("X" => { ++$x }); say $x'
> a1b2c3d
> 4
I created a pull r
The tests are passing now. I'm closing this ticket as 'resolved'.
'lift' was unspecced quite a while ago. I'm closing this ticket as 'rejected'.
This test failed because it assumed that +'3bc' evaluates to 3. The thing it
was supposed to test (state() within a regex) worked as expected.
I fixed und unfudged the test with commit
https://github.com/perl6/roast/commit/de2e5eaa77
The code used in this test died with X::AdHoc ("Too many positionals passed;
expected 0 arguments but got 1").
That is right thing, so I adjusted and unfudged the test with commit
https://github.com/perl6/roast/commit/f6fb6ab810
On Mon Oct 10 02:13:12 2011, masak wrote:
> On Sun Oct 09 09:10:12 2011, coke wrote:
> > On Thu Aug 12 14:35:18 2010, masak wrote:
> > > rakudo: role A { my $!foo; }; role B { my $!foo; };
> > > class C does A does B; say 'alive';
> >
> > 12:08 < [Coke]> rakudo: role A { my $!foo; }; role B { my
This test already had a ticket number:
https://rt.perl.org/Ticket/Display.html?id=77184. The test is fixed now.
Rejecting ticket.
These two tests were actually wrong. I changed them with commit
https://github.com/perl6/roast/commit/5afa99971e
This test was fixed with commit https://github.com/perl6/roast/commit/9a8babf191
To me this looks like the same problem as
https://rt.perl.org/Ticket/Display.html?id=124279
Actually, this also lead to spectest failures in S32-list/map.t and
S06-currying/named.t
I fudged the failing tests with commit
https://github.com/perl6/roast/commit/6302ae8ffa
There was already a ticket for these fudged tests:
https://rt.perl.org/Ticket/Display.html?id=76490 -- that's why I'm closing this
ticket.
There was already a ticket for this skipped test:
https://rt.perl.org/Ticket/Display.html?id=118407
There is a test for 'NaN ** 0' returning 0 in S02-types/nan.t skipped for the
reason 'unspecced and inconsistent'. Also there is a comment above the test:
# if we say that 0**0 and Inf**0 both give 1 (sse below), then for which
# number or limit whould $number ** 0 be different from 1? so maybe j
There are failing tests (fudged 'todo') in S04-phasers/in-loop.t and
S04-phasers/next.t, because LEAVE is called before NEXT.
S04 states that it should be the other way around:
"NEXT {...} at loop continuation time, before any LEAVE"
(http://design.perl6.org/S04.html#Phasers).
On Mon May 18 13:19:37 2015, barto...@gmx.de wrote:
> There is a test for 'NaN ** 0' returning 0 in S02-types/nan.t skipped
> for the reason 'unspecced and inconsistent'.
> [...]
> I'm inclined to change the test accordingly (expecting 1 as the
> result) and unfudge it.
I changed the test (and a s
This ticket is about skipped tests in S03-metaops/hyper.t and
S12-methods/parallel-dispatch.t which combine the unary hyper operator '>>'
with constant string subscripts for a Hash or Pair.
The following evaluation shows the problem:
$ perl6 -e 'say (a => 2, a => 3)>>.'
Cannot find method 'post
This ticket is about failing tests (fudged 'todo') in S06-other/main-usage.t
which are about using command line switches without '=':
$ perl6 -e 'sub MAIN(:$xin) { say $xin }' --xin "foo bar"
Usage:
-e '...' [--xin=]
According to S06 this should be valid and should be equivalent to
$ perl6 -e
On Mon Jun 16 07:26:32 2014, masak wrote:
> [...]
> * masak submits rakudobug
> r: say (gather for 1..3 { INIT take "OH HAI"; take $_ })
> rakudo-{jvm,moar} 6dd2e8: ( no output )
> ..rakudo-parrot 6dd2e8: OUTPUT«take without gather [...]»
> oh.
> Parrot may actually have a point.
>
> I think
This fails now with X::NYI and an adequate error message:
$ perl6 -e 'say callframe().callframe(1).my.perl'
Callframe.callframe not yet implemented. Sorry.
in block at -e:1
in any at -e:1
I wonder whether this ticket could be closed now or how a proper test would
look like.
As a status update: Nil is no longer an iterator:
$ perl6 -e 'say Nil.^mro'
Nil (Cool) (Any) (Mu)
But the recently introduced Empty is:
$ perl6 -e 'say Empty.^mro'
Empty (Iterator) (Iterable) Nil (Cool) (Any) (Mu)
I fixed and unfudged the failing tests with commit
https://github.com/perl6/roast/commit/ac628936cc
Hi,
quite a while ago you reported an issue with Rakudo Star segfaulting during the
install process for NetBSD packaging. Unfortunately noone had the time to hunt
that issue down back in 2013.
The error you reported seems to be specific for Rakudo on Parrot. Since support
for Parrot as a backe
This no longer fails:
$ perl6 -e 'my %h = classify { "foo" }, (); say "alive"'
alive
The tests were unfudged with commit
https://github.com/perl6/roast/commit/48fb065cf34eade25b782c0233fc04289c57fcc0
I'm closing this ticket as 'resolved'.
I added a test to S09-hashes/objecthash.t with commit
https://github.com/perl6/roast/commit/3f4554b157
I'm closing this ticket as 'resolved'.
The tests was unfudged with commit
https://github.com/perl6/roast/commit/de3372559d. I'm closing this ticket now.
I'm closing this ticket as 'resolved'. If you think, we should have a test for
this, please reopen the ticket.
There is a passing test in S32-num/sign.t. I'm closing this ticket as
'resolved'.
This was fixed with commits c79bcc5698 and 2cc3afe985.
I added a test to S05-metasyntax/regex.t with commit
https://github.com/perl6/roast/commit/e2259973be
I'm closing this ticket as 'resolved'.
As far as I understand it, the problem can be golfed to the following:
$ perl6 -e 'say EnumMap.new("a", 42).perl'
EnumMap.new(:a(42))
$ perl6 -e 'say EnumMap.new("a", 42).perl.perl'
"EnumMap.new(:a(42))"
$ perl6 -e 'say EnumMap.new("a", 42).perl.EVAL'
EnumMap.new()
This works now (with Rakudo commit 28a76979d9):
$ perl6 -e 'say all(1, 2, 3) ~~ Int' ## autothreads
all(True, True, True)
$ perl6 -e 'say all(1, 2, 3) ~~ Junction' ## does not autothread
True
There were tests added with roast commit 53f46867ee.
I'm closing this ticket as resolved.
After Rakudo commit a6d2edc644 this command dies (with X::AdHoc):
$ perl6 -e 'my $f = Sub.new(); say $f'
Cannot make a Sub object using .new
in block at -e:1
I added a test to S06-other/misc.t with commit
https://github.com/perl6/roast/commit/ff2dc709fd
I'm closing this ticket as 'resolved'.
I added a test to S09-typed-arrays/arrays.t with commit
https://github.com/perl6/roast/commit/e9694a7ef8.
I'm closing this ticket as 'resolved'.
Actually, there is a passing test in S19-command-line/arguments.t for this
specific example. Also, I think that there is consensus about the aim to
provide concise (and otherwise awesome) error messages (and to leave backtraces
to --ll-exception).
I'm closing this ticket as 'resolved' -- new bu
The first example works now as expected:
$ perl6-m -e 'sub foo ($a, $f) { if $f { foo("z", 0) }; given $a {say $a; say
$_} }; foo("x", 1)'
z
z
x
x
The second example works on rakudo.jvm but fails on rakudo.moar:
$ perl6-j -e 'sub foo ($a, $f) { if $f { foo("z", 0) }; {$_=$a; say $a; say $_}
};
This bug is still present. I added a test (fudged 'todo') to S32-array/pop.t
with commit https://github.com/perl6/roast/commit/046ad7e7e4
I tried the evaluation from this bug report and didn't get that internal error
anymore. There is still a type check error, though (which looks plausible to
me):
$ perl6-m -e 'sub p(*@l) { gather { if @l == 1 { take @l } else { @l.shift; for
p(@l) -> @p {} } } }; say p 1..4'
Type check failed in
I added a test to S04-exceptions/fail.t with commit
https://github.com/perl6/roast/commit/4366d917a5 and created a pull request for
Rakudo: https://github.com/rakudo/rakudo/pull/442
Now, the tests in S02-types/lazy-lists.t pass on rakudo.jvm as well.
I'm closing this ticket as 'resolved'.
The error message also mentions the operator now (and .gist still dies with
X::Numeric::DivideByZero):
$ perl6-m -e 'my $x = 1 % 0; say "still alive"; $x.gist'
still alive
Attempt to divide 1 by zero using infix:<%>
in block at -e:1
I added a test to S03-operators/arith.t with commit
https:
I added a test (fudged 'skip') to S12-attributes/instance.t with commit
https://github.com/perl6/roast/commit/dbf53cb4b1
AFAIU this inconsistency stems from using nqp::decont on attributes given to
.new (in src/core/Mu.pm), but not doing so on attributes given to .clone. I
added a PR (https://g
I added a test (fudged 'todo') to S12-attributes/instance.t with commit
https://github.com/perl6/roast/commit/dbf53cb4b1
The test passes now. I'm closing this ticket as 'resolved'.
I added a test for this to integration/weird-errors.t.
I'm closing this ticket as 'resolved'.
This test tried to set positional parameters by passing named arguments. Since
this feature went away, I adjusted and unfudged the test:
https://github.com/perl6/roast/commit/a9f6adf01a
I added a test to S09-hashes/objecthash.t with commit
https://github.com/perl6/roast/commit/9d5a3ec119
I'm closing this ticket as 'resolved'.
Tests were added to S32-array/delete.t and S32-array/delete-adverb.t. I'm
closing this ticket as 'resolved'.
On Tue Jun 23 02:43:41 2015, pesc...@gmail.com wrote:
> On Mon Feb 16 22:11:44 2015, coke wrote:
> > On Fri Mar 29 11:23:03 2013, coke wrote:
> > > On Fri Aug 31 12:10:54 2012, moritz wrote:
> > > > In nom, prefix and --> return type constraints weren't
> > > > implemented
> > > > for
> > > > quite
I added a test to integration/error-reporting.t with commit
https://github.com/perl6/roast/commit/766987b6de.
I'm closing this ticket as 'resolved'.
I added a test to 06-signature/introspection.t with commit
https://github.com/perl6/roast/commit/9a4daf7f91
Please note that the output no longer contains the type Any:
$ perl6-m -e 'sub foo($a;; $b) { say "OH HAI" }; foo(1, 2); say &foo.signature'
OH HAI
($a;; $b)
I'm closing this ticket as re
On Tue Jun 23 03:03:26 2015, mt1...@gmail.com wrote:
> [...]
> > Just to mention...
> >
> > Spectest 'S17-supply/start.t' fails on my system.
> >
> > $ uname -a
> > Linux h03-fedora 3.19.8-100.fc20.x86_64 #1 SMP Tue May 12 17:08:50
> > UTC 2015
> > x86_64 x86_64 x86_64 GNU/Linux
> >
> > $ perl6 -v
This works now on rakudo.jvm. On rakudo.moar 'foo(|%h, a => "c")' doesn't give
the correct result, yet:
$ perl6-j -e 'sub foo(*%p) { say %p.perl }; foo(a => "b", a => "c")'
{:a("c")}<>
$ perl6-j -e 'sub foo(*%p) { say %p.perl }; my %h = a => "b"; foo(|%h, a =>
"c")'
{:a("c")}<>
$ perl6-m -e 's
At first sight this looks good now:
$ perl6-j -e 'class Foo is repr { has int32 $.idontcare; has Foo $.bar
}; my $a = Foo.new; say "alive"'
alive
Unfortunatly, another NullPointerException surfaces when looking at the newly
created $a:
$ perl6-j -e 'class Foo is repr { has int32 $.idontcare; h
I added a simple test (only testing whether bare "await" dies, no check for the
error message) to S17-promise/basic.t with commit
https://github.com/perl6/roast/commit/305ca31ff7
I'm closing this ticket as 'resolved'.
On Tue Nov 20 12:16:04 2012, FROGGS.de wrote:
> looks good today:
>
> r: my Int @a = 1, 2, 3; my Str $x = "foo"; @a[0] := $x; say @a[0];
> rakudo bf472b: OUTPUT«foo»
>
> r: my Int @a = 1, 2, 3; my Int $x = 5; @a[0] := $x; say @a[0];
> rakudo bf472b: OUTPUT«5»
>
> r: my Int @a = 1, 2, 3; m
I just linked this ticket from
https://rt.perl.org/Ticket/Display.html?id=81682, which is now closed but
pointed to a similiar problem:
$ perl6-m -e 'my Int @a = 1, 2, 3; my Str $x = "foo"; @a[0] := $x; say @a[0];'
foo
It would be nice, if both variants (binding to a string directly and binding
On Mon Jun 29 14:21:31 2015, barto...@gmx.de wrote:
> Unfortunatly, another NullPointerException surfaces when looking at
> the newly created $a:
>
> $ perl6-j -e 'class Foo is repr { has int32 $.idontcare; has
> Foo $.bar }; my $a = Foo.new; say $a.bar'
> java.lang.NullPointerException
> in blo
It looks like this was not a bug regarding '|$' in a signature, but a
mis-parse. AFAIU commits https://github.com/rakudo/rakudo/commit/ce263122bc and
https://github.com/perl6/std/commit/53b3ca6ff2 changed the parsing rules for
rakudo and STD, respectively. The error messages are gone now:
< bar
I found this Pull Request for rakudo, which implemented the error message
"Slurpy positionals with type constraints are not supported":
https://github.com/rakudo/rakudo/pull/160
So I guess, the skipped tests for slurpy positionals in
S06-signature/slurpy-params.t should be replaced and the exam
AFAIU this ticket is about the type of @.slots not being respected. This seems
to be fixed now:
$ perl6 -e 'class A { has Method @.slots; }; A.new.slots.push: [1, 2, 3]'
Type check failed in assignment to '@!slots'; expected 'Method' but got 'Array'
in block at -e:1
I added a test to S32-arra
401 - 500 of 755 matches
Mail list logo