A lot of tests for colon--form radix overrides were added to
S02-literals/radix.t with commit 4c85334660. Those tests cover this ticket as
well. I mentioned the ticket number in said file.
I'm closing this ticket as 'resolved'.
This works now (fixed with commit ):
$ perl6-m -e '.squish(:with(-> $a, $b {1})).perl.say'
("a",).Seq
The tests in S32-list/squish.t are passing now. I'm closing this ticket as
'resolved'.
I don't grasp everything of the quoted discussion, but the original evaluation
works now as expected:
$ perl6 -e 'say (2/6).WHAT; say (2/6).perl.EVAL.WHAT'
(Rat)
(Rat)
A test was added to S32-scalar/perl.t with commit df84392d05.
Is this ticket closeable?
$ perl6-m -e 'sub a($a = CALLER::CALLER::<$_>) { say $a }; $_ = "foo"; a'
foo
$ perl6-m -e 'sub foo($a = CALLER::CALLER::<$_>) { say $a }; given 42 { foo(1);
foo() }'
1
42
The ticket number is mentioned in S06-signature/caller-param.t. The following
comment was added with commit 66a1ea8cb1:
#
The test this ticket is about was indeed unneccessarily restrictive. It was
removed with commmit https://github.com/perl6/roast/commit/c549562cbe
I'm closing this ticket as 'rejected'.
For the records: The second part of this error message was introduced recently
in response to RT #113888. I'm going to link both tickets as related.
The test this ticket refers to was removed with commit
https://github.com/perl6/roast/commit/a8f9dca88a ("remove obsolete overloading
tests ").
I'm closing this ticket as 'rejected'.
I rewrote the fudged tests with commit
https://github.com/perl6/roast/commit/c48ef39ea4. They pass now.
I'm closing this ticket as 'rejected.
I added a test to S06-other/main-usage.t with commit
https://github.com/perl6/roast/commit/f5a77ba56d
I'm closing this ticket as 'resolved'.
On Fri Sep 18 01:57:50 2015, elizabeth wrote:
> Fixed with d25a07a09d4ad4fa8d9e , test added with 3165b8c85b30c9710e2,
> can be closed
Great! I'm closing this ticket as 'resolved'.
I added two tests for [max] and .max with commit
https://github.com/perl6/roast/commit/76adbe5915
IntStr is tested in S02-literals/allomorphic.t
I'm closing this ticket as 'resolved'.
The test this ticket was about was fixed and unfudged with commit
https://github.com/perl6/roast/commit/30f08b143a.
I'm closing this ticket as 'resolved'.
The tests this ticket was about were fixed and unfudged with commit b318b44404.
I'm closing this ticket as 'resolved'.
The tests this ticket was about were fixed and unfudged with commit 8088700ce1.
I'm closing this ticket as 'resolved'.
This works now. Fixed with commit
https://github.com/rakudo/rakudo/commit/be02b7c955
The test in S03-metaops/hyper.t was unfudged with commit
https://github.com/perl6/roast/commit/124aef3530
I'm closing this ticket as 'resolved'.
On Sat Sep 12 01:35:43 2015, barto...@gmx.de wrote:
> A status update after the GLR:
>
> $ perl6 -e 'say Nil.^mro'
> (Nil (Cool) (Any) (Mu))
>
> $ perl6 -e 'say Empty.^mro'
> ((Slip) (List) (Cool) (Any) (Mu))
>
> So neither Nil nor Empty is Iterator anymore.
I just saw that there is a
The test this ticket refers to was removed with commit
https://github.com/perl6/roast/commit/a8f9dca88a ("remove obsolete overloading
tests ").
I'm closing this ticket as 'rejected'.
On Mon Nov 30 07:55:28 2015, elizabeth wrote:
> Thank you for the report! Fixed with 437ef184ee86fc04d4ecdd , can be
> closed
Thanks. I'm closing this ticket as 'resolved'.
The test passes (again).
$ perl6-j -e 'say (1..*).Capture.perl'
\(:max(Inf), :min(1))
I'm closing this ticket as 'resolved'-
The test in S10-packages/precompilation.t now passes on rakudo.JVM, also.
I'm closing this ticket as 'resolved'.
Looks like this has nothing to do with lib/Test.pm:
$ echo '#' > Bar.pm6
$ ./perl6-m -I. -e 'use Bar; my %h = b => 2; say %h:zorp'
Unexpected named parameter 'zorp' passed
in block at -e:1
$ ./perl6-m -I. -e 'use Bar; my %h = b => 2; say %h:zorp'
2
Setting RAKUDO_MODULE_DEBUG=1 does still
Another data point: The evaluation works as expected with MVM_SPESH_DISABLE=1:
$ echo '#' > Bar.pm6
$ MVM_SPESH_DISABLE=1 ./perl6-m -I. -e 'use Bar; my %h = b => 2; say %h:zorp'
Unexpected named parameter 'zorp' passed
in block at -e:1
$ MVM_SPESH_DISABLE=1 ./perl6-m -I. -e 'use Bar; my %h =
This works now as expected:
$ perl6-j -e 'for 1 { last; ENTER { say "hurz" } }'
hurz
I added a test to S04-phasers/in-loop.t (and unfudged the skipped tests there)
with commit https://github.com/perl6/roast/commit/da7ff73062
I'm closing this ticket as 'resolved'.
The tests in question were removed with commit
https://github.com/perl6/roast/commit/61758a2278
I'm closing this ticket as 'rejected'.
On Thu Dec 24 01:37:47 2015, elizabeth wrote:
>
> Fixed with fb475d22ba6d5507dd4db , test added with
> 7e5f5db4e12a07701c4da .
Great! I'm closing the ticket as 'resolved'.
On Thu Dec 24 19:26:55 2015, zef...@fysh.org wrote:
> This has now been fixed by commit 986f98d8c6d772ac5d0b513793c521df6a343ae8
> from Timo++.
>
> -zefram
Thanks! I added at test to S32-exceptions/misc.t with commit
https://github.com/perl6/roast/commit/b0c17ab00c
I'm closing this ticket as
On Wed Dec 23 15:00:46 2015, elizabeth wrote:
>
> Fixed in 18947f4249aa0c11a1f1ac3 , test added with
> 38e988158507ee040ab33e .
>
> Can be closed.
Great! I'm closing the ticket as 'resolved'.
On Wed Dec 23 15:52:29 2015, elizabeth wrote:
>
> Fixed with 895546990f6001a5999ef , tests added with
> 0fa2c59924a35bb41e792
>
>
> Can be closed.
Great! I'm closing the ticket as 'resolved'.
On Wed Jan 06 13:51:56 2016, elizabeth wrote:
[...]
> Fixed with 70640bf , tests added with 4a59ba3 , can be closed
Thanks! I'm closing this ticket as 'resolved'.
On Tue Jan 05 03:55:57 2016, elizabeth wrote:
[...]
> Fixed with d80c728e257dbe17384c4 , test unfudged with 233d409 , can be
> closed.
Thanks! I'm closing this ticket as 'resolved'.
On Sat Jan 02 15:19:11 2016, elizabeth wrote:
> > On 02 Jan 2016, at 20:54, Dan Kogai (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Dan Kogai
> > # Please include the string: [perl #127126]
> > # in the subject line of all future correspondence about this issue.
> > #
On Wed Jan 06 06:05:47 2016, elizabeth wrote:
[...]
> Fixed with fec0619 , tests added with 5e7d2ad , can be closed.
Thanks! I'm closing this ticket as 'resolved'.
On Tue Jan 05 01:28:09 2016, elizabeth wrote:
[...]
> Fixed with 18957e3f98e7830eb0c , tests added with afe667b , can be
> closed
Thanks! I'm closing this ticket as 'resolved'.
On Tue Jan 05 01:11:37 2016, elizabeth wrote:
[...]
> Fixed with d1ff735 , tests added with b774bcc , can be closed
Thanks! I'm closing this ticket as 'resolved'.
I just found that my golfed test case seems to be flapping:
$ for run in {1..10}; do (echo '#' > Bar.pm6; ./perl6-m -I. -e 'use Bar; my %h
= b => 2; say %h:zorp' 2>&1; ./perl6-m -I. -e 'use Bar; my %h = b => 2; say
%h:zorp' 2>&1) | grep -c 'Unexpected named parameter'; done
2
2
1
2
1
2
1
1
2
1
The test this ticket was about was unfudged with commit
https://github.com/perl6/roast/commit/734565c16e
I'm closing this ticket as 'resolved'.
I changed the tests to not expect a specific order with commit:
https://github.com/perl6/roast/commit/f1df147714
I'm closing this ticket as 'resolved'.
The tests in S32-io/spurt.t are passing (again) on rakudo.jvm.
I'm closing this ticket as 'resolved'.
Current behaviour:
$ perl6-m -e 'my $r1 = role { method foo() { 5 } }; my $r2 = role { method
foo() { 7 } }; my %hash{Any}; %hash{"quux" but $r1} = 9; %hash{"quux" but $r2}
= 11; say %hash.keys>>.foo'
(5 7)
Is that the expected answer?
As a status update: There is no NPE anymore:
$ ./perl6-j
> True ~~ True
Potential difficulties:
Smartmatch against True always matches; if you mean to test the topic for
truthiness, use :so or *.so or ?* instead
at :1
--> True ~~⏏ True
TrueTrue
>
On Sat Nov 28 07:49:05 2015, barto...@gmx.de wrote:
> There was a short discussion on #perl6 about this recently:
> http://irclog.perlgeek.de/perl6/2015-11-17#i_11554013
>
> ZoffixW How come $! is empty?
> m: my ( $v1, $op, $v2 ) = (2, '-', "zoffix"); my $x =
> try { EVAL
This works now:
$ perl6-m -e 'class A { has @.a of int }; my $foo = A.new; $foo.a = 1,2,3; say
$foo.perl'
A.new(a => array[int].new(1, 2, 3))
Also, there is no NPE with the REPL:
$ echo 'class A { has @.a of int }' | perl6-j
> >
I added a test to S12-class/attributes.t with commit
There was a short discussion on #perl6 about this recently:
http://irclog.perlgeek.de/perl6/2015-11-17#i_11554013
ZoffixW How come $! is empty?
m: my ( $v1, $op, $v2 ) = (2, '-', "zoffix"); my $x = try {
EVAL "$v1 $op $v2"; CATCH { fail "Invalid operand to Color: Got
On Sun Nov 29 03:54:18 2015, elizabeth wrote:
> Tests fixed, don’t think further tests are needed
Great, I'm closing this ticket as 'resolved'.
The problem was, that .sort was broken on rakudo.jvm.
That was fixed with commit https://github.com/rakudo/rakudo/commit/5da0b3faed
Tests are unfudged again and I'm closing this ticket as 'resolved'.
The failing tests on JVM behave correctly, when executed on the command line:
$ perl6-j -e 'my $data = "f fo foo fooo f fo foo"; $data ~~
m:nth(-1)/fo+/; say "alive"'
Attempt to retrieve before :1st match -- :nth(-1)
in block at -e:1
The same code in the test file (using
The problem was, that .sort was broken on rakudo.jvm.
That was fixed with commit https://github.com/rakudo/rakudo/commit/5da0b3faed
Tests are unfudged again and I'm closing this ticket as 'resolved'.
The problem was, that .sort was broken on rakudo.jvm.
That was fixed with commit https://github.com/rakudo/rakudo/commit/5da0b3faed
Tests are unfudged again and I'm closing this ticket as 'resolved'.
This seems to work now:
$ perl6 -e 'say "foo foo foo".subst(/foo/, "bar", :nth(-Inf));'
Attempt to retrieve before :1st match -- :nth(-Inf)
in block at -e:1
skids++ added tests with commit e502eaf9.
For some reason a few of those tests still fail (do not die) on rakudo.jvm.
I'll flag this
The same thing happens in S32-array/adverbs.t.
I fudged some more tests with this error mode in S32-list/squish.t
The error happens in /src/core/Mu.pm when binding to @a in the signature of
this sub definition:
multi sub infix:(@a, @b) {
...
}
Moar and JVM behave differently when trying to bind a Seq in such a case:
$ perl6-m -e 'sub foo
The test in S14-roles/basic.t passes now on JVM.
Also the code from lizmat++ does not die:
$ perl6 -e 'role R { method !m(@a) { say "ok: @a[]" }; method x() { self!m((my
%).values) } }; class C does R { }; C.x'
ok:
I haven't yet looked at src/core/IO/Local.pm or src/core/Temporal.pm
After Rakudo commit negative start positions are disallowed:
$ perl6 -e 'say index("xxy", "y", -1).perl'
Failure.new(exception => X::OutOfRange.new(what => "Position in index", got =>
-1, range => "0..3", comment => Any), backtrace => Backtrace.new)
Tested in S32-str/index.t and
It looks like the overflow still happens. (Expected result is different
nowadays, since negative start positions are disallowed (see
https://github.com/rakudo/rakudo/commit/fa3ce116e3).
See also http://irclog.perlgeek.de/perl6/2015-11-21#i_11577908
$ perl6-m -e 'say index("xxy", "y",
Thanks! I'm closing this ticket as 'resolved'.
Great. I unfudged the tests with commit
https://github.com/perl6/roast/commit/e2174a8adf.
I'm closing this ticket as 'resolved'.
Most of the tests in S02-types/array-shapes.t pass now (unfudged/adjusted with
commit https://github.com/perl6/roast/commit/4a5edf73db).
Maybe the other tests should be reviewed?
On Sat Jun 04 13:30:58 2016, barto...@gmx.de wrote:
>
> I'm not really sure, but I think the NPE happens because somewhere in
> 'sub map' or 'method map' is a call to .list and we end up in
> List.iterator.
Ah, here (src/core/Any-iterable-methods.pm:1371) is what made me assume that
map caused
On Sat Jun 04 13:20:25 2016, elizabeth wrote:
> The weird thing here is, is that somehow the List.iterator is used,
> instead of the Array.iterator (which *does* take null values into
> account, even makes them bindable)
>
> Is this still a problem on HEAD ?
Oops, didn't see your reply before
On Sat Jun 04 14:10:20 2016, barto...@gmx.de wrote:
>
> Ah, here (src/core/Any-iterable-methods.pm:1371) is what made me
> assume that map caused us to end up in List.iterator -- values seems
> to be a List here:
>
> multi sub map(, +values) { my $laze = values.is-lazy;
>
As a follow-up: The following code works as expected:
$ perl6-j -e 'my @a; @a[0;1] = "foo"; @a[0;0] = "bar"; say @a.perl'
[["bar", "foo"],]
On Fri May 27 04:40:05 2016, elizabeth wrote:
>
> > The following code started to fail on rakudo-j:
> >
> > $ perl6-j -e '(3/0).Num'
> > java.lang.ArithmeticException: BigInteger divide by zero
> > in block at -e line 1
> >
> > The test still passed on commit a5c46bb7f4 (2016-05-25) and fails on
On Tue Jan 12 06:35:56 2016, coke wrote:
> [...]
> > So, is this ticket closable?
>
> Yes, thanks.
Great. I'm closing the ticket as 'resolved'.
I'm closing this ticket, since it's a duplicate of
https://rt.perl.org/Ticket/Display.html?id=127394.
The author of this ticket reported a golfed version of this bug as
https://rt.perl.org/Ticket/Display.html?id=127682
As requested in that new ticket, I'm closing (rejecting) this ticket.
On Fri Apr 08 05:56:54 2016, pesc...@gmail.com wrote:
>
> This was fixed in rakudo commit 0c78181 and the test file now passes
> on R-J.
Thanks a lot! I'm closing this ticket as 'resolved'.
The pull request was merged. I'm closing this ticket as 'resolved'.
I was able to reproduce the problem with rakudo 2016.01.1 on Linux.
It seems to be fixed now (maybe with rakudo commit 241e5e5847):
$ ls -lh 126372.data
-rw-r--r-- 2 christian christian 48M Apr 11 14:07 126372.data
$ time ./perl6-m -e 'my $content = slurp "126372.data", :bin; say
This fails now with X::Method::NotFound and the error message has some more
informations:
$ perl6-m -e '*(42)'
No such method 'CALL-ME' for invocant of type 'Whatever'
in block at -e line 1
I added a simple test to S02-types/whatever.t with commit
The implementation has changed with rakudo commit f220a5ed so that Int() is
called on $k (and $n).
The examples work consistently now, but it looks like there are no tests for
this in roast:
$ perl6-m -e 'say combinations 2, 0.5'
(())
$ perl6-m -e 'say combinations 2, 1.5'
((0) (1))
$
The test was relaxed with commit
https://github.com/perl6/roast/commit/a069b922c9 (6.c-errata branch).
I'm closing this ticket as 'resolved'.
Both failing tests where removed with commit
https://github.com/perl6/roast/commit/c73db6b5c1 (6.c-errata branch).
I'm closing this ticket as 'resolved'.
All blockers have been dealt with and the release was done in time. I'm closing
this ticket was 'resolved'.
The faulty test was fixed in the 6.c-errata branch with commit 6af3c5b5de.
I'm closing this ticket as 'resolved'.
On Sat Jan 02 13:14:43 2016, david.warring wrote:
> This could be a bit of a non-issue in Perl 6.c, which handles
> precompilation and gets this right:
>
> $ perl6 --version
> This is Rakudo version 2015.12-72-g3ea4dff built on MoarVM version
> 2015.12
> implementing Perl 6.c.
> $ $ perl6-m -I
On Sat Apr 02 11:08:03 2016, steve.mynott+bitc...@gmail.com wrote:
>
> Fixed in ae3bf37
Tanks! I'm closing this ticket as 'resolved'.
On Fri Apr 08 05:51:16 2016, pesc...@gmail.com wrote:
>
> This has been fixed in Rakudo commit ec52cce:
> $ ./perl6-j --version
> This is Rakudo version 2016.03-99-g46388f4 built on JVM
> implementing Perl 6.c.
> $ ./perl6-j -e'[[2,3],[4,[5,6]]]>>.squish.say'
> ((2 3) (4 [5 6]))
Great. I
There is no NullPointerException in the REPL anymore:
$ perl6-j
To exit type 'exit' or '^D'
> constant %a is export = 5 => 5; constant %a is export = 5 => 5
===SORRY!=== Error while compiling
Redeclaration of symbol %a
at :2
--> ⏏
>
I'm closing this ticket as 'resolved'.
I addes a test to S32-list/permutations.t with commit
https://github.com/perl6/roast/commit/30db58671d
I'm closing this ticket as 'resolved'.
I added the above examples as tests to S02-types/array-shapes.t with commit
https://github.com/perl6/roast/commit/a2617480f4
I'm closing this ticket as 'resolved'.
I opened a small PR for Rakudo (https://github.com/rakudo/rakudo/pull/740) to
remove the relevant section from README.md and to add a warning that
docs/compiler_overview.pod is not up to date.
I thought about adding a test for this ticket, but now wonder what the expected
output for the evaluation is.
As Moritz showed a current Rakudo complains about 'Useless use of "+" in
expression "$a + $b" ...'.
In masak's original example the warning was about "Useless use of variable $a
...".
This works consistently now:
$ perl6-m -e '.say for combinations -999, 2'
()
$ perl6-m -e '.say for combinations -99, 2'
()
Calling combinations with a negative $k gives an empty list:
$ perl6-m -e 'say combinations 4, -2'
()
I added tests for this behaviour to
On Sun Apr 10 14:01:06 2016, alex.jakime...@gmail.com wrote:
> This can be closed. See https://github.com/rakudo/rakudo/pull/737
Thanks. I'm closing this ticket as 'resolved'.
My golfed test cases do no longer fail.
$ for run in {1..10}; do (echo '#' > Bar.pm6; ./perl6-m -I. -e 'use Bar; my %h
= b => 2; say %h:zorp' 2>&1; ./perl6-m -I. -e 'use Bar; my %h = b => 2; say
%h:zorp' 2>&1) | grep -c 'Unexpected named parameter'; done
2
2
2
2
2
2
2
2
2
2
Alas, the tests in
On Sun Apr 24 02:45:35 2016, barto...@gmx.de wrote:
> Alas, the tests in S32-hash/adverbs.t and S32-array/adverbs.t still do
> not pass. Will try to find a new/better golf.
Not as short as I hoped (it needs Test.pm6), but this is what currently fails
in S32-hash/adverbs.t:
$ perl6-m -Ilib -e
On Thu Apr 21 05:54:59 2016, barto...@gmx.de wrote:
> The (somewhat) golfed code is:
>
> $ perl6-j -e 'say < 8+9i > eqv ComplexStr.new(<8+9i>, "8+9i")'
Actually the same error occurs with
$ perl6-j -e 'say < 8+9i >.re'
Attribute '$!re' is not a native num
in block at -e line 1
On Thu Apr 21 11:53:14 2016, barto...@gmx.de wrote:
>
> $ perl6-j -e 'say < 8+9i >.re'
> Attribute '$!re' is not a native num
> in block at -e line 1
Oh, looks like rakudo-j has other problems with the attributes of ComplexStr:
$ perl6-j 'say < 8+9i >.im'
8
For the records: There is a test for this ticket (currently fudged 'todo') in
S06-other/main-usage.t
On Thu Apr 21 04:41:32 2016, barto...@gmx.de wrote:
> [...]
> A somewhat golfed example of the hanging code is:
>
> $ perl6-j -e 'my $r = Supplier.new; my $s = $r.Supply; my $c =
> $s.Channel; my $p = start { for @$c { } }; for 1..4 { $r.emit($_); };
> $r.quit(X::AdHoc.new(:payload("foo"))); try
On Wed May 11 00:51:48 2016, elizabeth wrote:
> Doesn’t this imply that prefix ++ on native ints is broken on the JVM.
> And thus, a lot of more got broken recently due to my changes??
That was my first thought, too. But this was the only place where rakudo-j got
a hickup. Prefix++ works fine in
As a status update: things are substantially better now (2016.04-218-gaa2715d)
-- thanks to nine++
and psch++
+ stresstest runs in a reasonable time again (precompiled Test.pm can be used)
+ test for RT #114354 passes again
+ FIRST works now
The remaining issues are:
- 'make install' still
The tests for FIRST pass now, psch++.
I unfudged the tests with commit
https://github.com/perl6/roast/commit/ce7363836a and I'm closing this ticket as
'resolved'.
I found another strange test failure on rakudo-j related to the use
of prefix:<++>: The test in integration/weird-errors.t (which I
fudged with roast commit ca3abdefb1) started to fail with rakudo
commit e2fcdf2702.
The test in isolation works fine, but the failure happens in
combination with
On Sat Oct 31 20:31:41 2015, coke wrote:
> See S03-operators/buf.t
>
> Both of these fail:
>
> ok $a ~ $b eq Buf.new(1, 2, 3, 1, 2, 3, 4), '~ and eq work on bufs';
> is-deeply Buf.new(1, 2, 3) ~ Buf.new(4, 5), Buf.new(1, 2, 3, 4, 5), '~
> concatenates';
These tests pass now (again). I'm closing
This works now (again):
$ perl6-j -e 'my Blob $a = "a".encode; my Blob $b = "b".encode; $a ~= $b; say
$a.perl'
utf8.new(97,98)
I added this evaluation as a test to S03-operators/buf.t. I'm closing this
ticket as 'resolved'.
This has been fixed in MoarVM (commits b4d1dc653e and 987923343c).
MoarMV and NQP versions were bumped and Rakudo builds again on platforms using
clang. I'm closing this ticket as 'resolved'.
Sorry, I got a bit confused:
The different behavior for routines index and rindex with negative
startposition between rakudo-moar and rakudo-jvm was fixed (see
https://rt.perl.org/Ticket/Display.html?id=126700).
What's still relevant is the different implementation of nqp::index:
$ perl6-m -e
The problems regarding negative overflows seem to be fixed. All tests for this
ticket are passing. I'm closing this ticket as 'resolved'.
For the related discussion (different behavior of nqp::index with negative
$startpos between Moar and JVM) I opened a new ticket:
This ticket is about two currently skipped tests in
S03-operators/flip-flop.t.
The tests in question check how often the left hand side (lhs) and
right hand side (rhs) are evaluated against $_ when using the
operators 'ff' and 'fff', respectively:
# make sure {lhs,rhs} isn't evaluated when state
501 - 600 of 752 matches
Mail list logo