This now works on the JVM backend, too. Fixed with
https://github.com/rakudo/rakudo/commit/12d4514a3d
I'm closing this ticket as 'resolved'.
This is still a problem on the JVM backend. I tried a second time to find the
underlying problem and arrived at the same conclusion: There seems to be
something wrong in 'analyze_dispatch'. When running the given code
multi foo ($) {"right" }; multi foo ($ is rw) {"wrong"}; say foo "42"
'anal
Using spaces in prefix path should work now. There was some serious revamp of
the build system during the last couple of months. I didn't have all the
details, but some relevant pull requests for Rakudo have probably been:
* https://github.com/rakudo/rakudo/pull/2693
* https://github.com/rakudo/r
On Sun, 31 Jul 2016 19:14:19 -0700, c...@zoffix.com wrote:
> Can't reproduce the issue.
>
> Are you able to try again with the latest Rakudo, please?
Since there was no update on this ticket, I'm closing (rejecting) it now. I'm
pretty sure we'd have more bug reports if this would be an issue wit
Back in 2017 jnthn++ already added a test for lazy for loops with
https://github.com/perl6/roast/commit/3659ede149. Since the evaluations in this
ticket also take the type into considerations, I've added a new test to
S32-list/seq.t with https://github.com/perl6/roast/commit/207171b5ee
I'm clos
I've added a test to S02-names/pseudo-6e.t with
https://github.com/perl6/roast/commit/73d867501c
I'm closing this ticket as 'resolved'.
The skip directive has been removed (at least for v6.e) with commit
https://github.com/perl6/roast/commit/04c7d09341 (see also
https://github.com/perl6/roast/commit/2913fbe564 for v6.c and v6.d).
I'm closing this ticket as 'rejected', since there wasn't added any additional
information.
These tests have been adjusted with
https://github.com/perl6/roast/commit/551a7ffd7b
I'm closing this ticket as 'resolved'.
This test works with more recent Java version, cmp.
https://github.com/perl6/roast/commit/b5c4ed2345
I'm closing this ticket as 'resolved'.
This test works now, cmp. https://github.com/perl6/roast/commit/472bc003f0
I'm closing this ticket as 'resolved'.
The test in question works now, cmp.
https://github.com/perl6/roast/commit/bba5083af5.
I'm closing this ticket as 'resolved'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
I have committed https://github.com/perl6/nqp/commit/59d7a8869c and this test
passes now.
As far as I understand, the right handler was missed when moving to the
outside, because unwind_check sets the outer handler to 0 by default if no
outer handler is passed. We do the latter now.
I'm closin
As jmerelo++ pointed out [1] the statement prefix 'lazy' has been fixed back in
2015 with https://github.com/rakudo/rakudo/commit/d043961414. It no longer
shares the implementation with 'do'.
The tests that are fudged with this ticket don't work, though. The test file
S04-statements/lazy.t is n
On Thu, 04 Apr 2019 22:59:38 -0700, barto...@gmx.de wrote:
> I'm going to unfudge the test in S02-magicals/sub.t for rakudo.jvm.
For the record: https://github.com/perl6/roast/commit/aaf7ad02fc
On Thu, 04 Apr 2019 23:09:43 -0700, barto...@gmx.de wrote:
> I'm going to unfudge the test in S32-str/length.t and close this ticket.
For the record: https://github.com/perl6/roast/commit/aaf7ad02fc
On Thu, 04 Apr 2019 23:15:25 -0700, barto...@gmx.de wrote:
> I'm going to change two skipped tests to 'todo'.
For the record: https://github.com/perl6/roast/commit/aaf7ad02fc
Just for the record: This seems to work on the JVM backend:
$ ./perl6-j --optimize=3 -e 'sub f() { sub g() { if True { return
&?ROUTINE.name } } }; say f()()'
g
I'm going to unfudge the test in S02-magicals/sub.t for rakudo.jvm.
After https://github.com/rakudo/rakudo/commit/704b893c6a the last tests fudged
with this ticket are passing. I'm closing this ticket as 'resolved'.
https://github.com/rakudo/rakudo/issues/1361 has been fixed back in February
2018.
All three code snippets from this issue are failing with
X::Syntax::Variable::BadType now.
I've added a test to S12-coercion/coercion-types.t with commit
https://github.com/perl6/roast/commit/7fcc804bb9.
I'm cl
I'm closing this ticket, cmp. https://github.com/rakudo/rakudo/issues/1797:
> #124552 can be closed. Test was working but skipped. Unskipped in roast now.
This has been fixed with https://github.com/perl6/nqp/commit/075ff765f5
The test in S05-mass/rx.t passes, so I'm closing this ticket was 'resolved'.
This has been fixed with https://github.com/perl6/nqp/commit/075ff765f5
The tests in S05-metasyntax/lookaround.t are passing, so I'm closing this
ticket was 'resolved'.
I'm closing this ticket, cmp. https://github.com/rakudo/rakudo/issues/1797:
> #124738 can be closed because the roast test was wrong, trying to use a m//
> where an rx// was intended.
> Fixed by samcv in roast commit
> https://github.com/perl6/roast/commit/659fcf44b0
On Thu, 13 Apr 2017 12:21:57 -0700, barto...@gmx.de wrote:
> [...] then we should
>
> * change the implementation for the JVM backend so that the newly
> added tests pass
The tests for open modes are passing now on the JVM backend. I'm closing this
ticket as 'resolved'.
On Mon, 29 Jan 2018 03:54:38 -0800, pesc...@gmail.com wrote:
> On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote:
> > On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote:
> > > I managed to golf this a bit:
> > >
> > > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () {
>
On Sat, 10 Mar 2018 11:40:24 -0800, barto...@gmx.de wrote:
> On Thu, 13 Apr 2017 12:21:57 -0700, barto...@gmx.de wrote:
> > [...]
> > * define that :append and :create always imply "write"
>
> That was also done by Zoffix++ -- mainly with
> https://github.com/perl6/roast/commit/091931a717
Sorry,
On Thu, 13 Apr 2017 12:21:57 -0700, barto...@gmx.de wrote:
> [...]
> * define that :append and :create always imply "write"
That was also done by Zoffix++ -- mainly with
https://github.com/perl6/roast/commit/091931a717
On Thu, 13 Apr 2017 12:21:57 -0700, barto...@gmx.de wrote:
> [...]
> * expand the documentation of "open"
That was done by Zoffix++ with https://github.com/perl6/doc/commit/ca2a3a0bfb
On Sat, 27 Jan 2018 17:19:18 -0800, pesc...@gmail.com wrote:
> On Sat, 21 Nov 2015 06:12:07 -0800, barto...@gmx.de wrote:
> > The following code does not give the expected result ('2') on
> > rakudo.jvm:
> >
> > $ perl6-j -e 'multi catch(| (*@all ) ) { 1 }; multi catch(| (*@all,
> > :$really! ) ) {
On Fri, 10 Feb 2017 23:48:54 -0800, barto...@gmx.de wrote:
> FWIW that hangs on FreeBSD as well (maybe not too much a surprise,
> given the relationship of the OSes).
Hmm, looks like it hangs on Linux too -- with more than 224000 bytes on my
machine:
$ perl6 -e 'my $proc = run($*EXECUTABLE, "-e"
On Fri, 10 Feb 2017 23:48:54 -0800, barto...@gmx.de wrote:
> FWIW that hangs on FreeBSD as well (maybe not too much a surprise,
> given the relationship of the OSes).
This still hangs on MoarVM, but works on JVM (I didn't check the behaviour on
JVM last year):
$ ./perl6-j -e 'my $proc = run($*EX
On Sun, 28 May 2017 13:09:18 -0700, barto...@gmx.de wrote:
> Currently rakudo on JVM does not respect eof when reading from stdin.
>
> bartolin_ r: .say for lines()
> camelia rakudo-moar 094e77: OUTPUT: «»Wann treffen wir drei
> wieder zusamm?« »Um die siebente Stund‘, am Brückendamm.
On Tue, 16 Jan 2018 00:30:47 -0800, c...@zoffix.com wrote:
> On Sun, 14 Jan 2018 02:14:57 -0800, c...@zoffix.com wrote:
> > On Sat, 13 Jan 2018 23:51:44 -0800, barto...@gmx.de wrote:
> > > On Wed, 10 Jan 2018 17:32:30 -0800, c...@zoffix.com wrote:
> > > > Thank you for the report. This is now fixed
On Wed, 10 Jan 2018 17:32:30 -0800, c...@zoffix.com wrote:
> Thank you for the report. This is now fixed.
>
> Fix: https://github.com/rakudo/rakudo/commit/c6b7012a9c61133
> Test: https://github.com/rakudo/rakudo/commit/c6b7012a9c61133
For the records: The Rakudo fix made some previously passing
This was fixed with https://github.com/perl6/nqp/commit/f6bccf79d8
Only some of the fudged tests are passing now, since a different issue surfaced
after the above fix: https://rt.perl.org/Ticket/Display.html?id=132694
I'm closing this ticket as 'resolved'.
On Sat, 31 Oct 2015 20:35:24 -0700, coke wrote:
> Many tests in S03-operators/increment.t are throwing ad hoc exceptions
> instead of X::Parameter::RW
There have been some changes in this area:
1) With roast commit https://github.com/perl6/roast/commit/93736e7f73 the
failing tests have been chan
This works now as expected:
m: sub Foo(uint32 :$bar) { say $bar }; Foo(:bar(4))
rakudo-moar ae6177ca2: OUTPUT: «4»
I think, it was fixed with https://github.com/perl6/nqp/commit/fc727ea911
(bisectable pointed to the corresponding NQP bump).
Since the tests in S02-types/native.t are pass
Just for the records: As far as I can tell, the bug that caused the above
failures was an "off by one" in the multi cache implementation. It was fixed
with https://github.com/perl6/nqp/commit/7eaebf5abd
There was indeed something wrong with the multi cache on the JVM backend. Fixed
with https://github.com/perl6/nqp/commit/7eaebf5abd
I'm closing this ticket as 'resolved'.
There was something wrong with the multi cache on the JVM backend. Fixed with
https://github.com/perl6/nqp/commit/7eaebf5abd
I'm closing this ticket as 'resolved'.
There was indeed something wrong with the multi cache on the JVM backend. Fixed
with https://github.com/perl6/nqp/commit/7eaebf5abd
I'm closing this ticket as 'resolved'.
On Tue, 28 Nov 2017 12:35:42 -0800, barto...@gmx.de wrote:
> [...]
> I tried to golf the failures from set_addition.t and found the
> following:
>
> $ ./perl6-j --ll-exception -e '&infix:<(+)>(SetHash.new, SetHash.new,
> SetHash.new); &infix:<(+)>(|(Set.new, Set.new, Set.new));
> &infix:<(+)>(|(Se
On Fri, 01 Dec 2017 10:57:33 -0800, alex.jakime...@gmail.com wrote:
> It is actually fixed now:
>
> ¦2015.12,b2fbf893db^:
> «-1100100»
>
> ¦b2fbf89,HEAD(5929887):
> «-1100100»
>
> That
The test in question passes now.
< bartolin> bisectable6: say "ab" ~~ rx:P5/^(a(??{"(?!)"})|(a)(?{1}))b/ &&
$1 # RT 125027
< bisectable6> bartolin, Bisecting by exit code (old=2015.12 new=5929887).
Old exit code: 1
<+synopsebot>RT#125027 [new]:
https://rt.perl.org/Ticket/Display.html
This works now on the JVM backend as well (test in
S05-match/capturing-contexts.t is passing). Fixed with nqp commit
https://github.com/perl6/nqp/commit/f22b0b2d0e
I'm closing this ticket as 'resolved'.
This works now on the JVM backend as well. I've unfudged the old tests and 've
added one test with a P6 regex to S05-metasyntax/regex.t with commit
https://github.com/perl6/roast/commit/ae57169b24
I'm closing this ticket as 'resolved'.
On Thu, 21 Sep 2017 16:27:09 -0700, b...@abrij.org wrote:
> On Sat, 05 Aug 2017 06:28:34 -0700, jan-olof.hen...@bredband.net
> wrote:
> > On Wed, 05 Oct 2016 14:23:57 -0700, c...@zoffix.com wrote:
> > >
> > > This code shows the bug:
> > >
> > > zoffix@leliana:~$ perl6 -e 'm: multi foo ($) {"right"
The tests in S32-array/adverbs. and S32-hash/adverbs.t (and all code snippets
in this ticket) are passing again. I'm closing this ticket as 'resolved'.
The tests in question are passing again.
I'm closing this ticket as resolved.
There was a report for similar test failures on Solaris on #moarvm today:
https://irclog.perlgeek.de/moarvm/2017-10-20#i_15328975
Also, we had ticket #69464 (rejected) with a similar report for OpenSolaris.
I'm going to add solaris as a platform to this ticket.
On Sat, 16 Jul 2016 13:18:42 -0700, barto...@gmx.de wrote:
> I unfudged one test for this ticket in S04-statements/label.t with
> commit https://github.com/perl6/roast/commit/ef7b0da83d
>
> The code that used to segfault works fine now:
>
> $ perl6-m -e 'A: for 1 { for 1 { last A }; CONTROL { whe
On Sat, 23 Sep 2017 12:28:53 -0700, barto...@gmx.de wrote:
> 3) Feeding the EvalServer with a program that calls 'run' (or
> Proc::Async directly) does heavily leak memory, threads and what not
> (again assuming a clean EvalServer instance started as above):
>
> $ echo 'run("echo", "42");' > foo.p
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 Mon, 18 Sep 2017 14:00:02 -0700, barto...@gmx.de wrote:
> On Sat, 16 Sep 2017 08:46:00 -0700, barto...@gmx.de wrote:
> > Here is a simple example:
> >
> > $ ./perl6-j -e 'try { die "foo" }; say $!.perl; say $!.gist'
> > X::AdHoc.new(payload => "foo")
> > Died
> > in block at -e line 1
>
>
>
On Sat, 16 Sep 2017 07:27:48 -0700, alex.jakime...@gmail.com wrote:
> From this discussion https://irclog.perlgeek.de/perl6-dev/2017-09-
> 16#i_15171820
>
> 1) 'make' does not work before 'make install': I believe that happens,
> because we use the EvalServer -- and that doesn't look for
> BOOTSTR
On Sat, 16 Sep 2017 07:31:18 -0700, alex.jakime...@gmail.com wrote:
> From this discussion https://irclog.perlgeek.de/perl6-dev/2017-09-
> 16#i_15171820
>
> 4) the EvalServer seems to leak memory. it's no longer possible to run
> 'make spectest', even with -Xmx6000m
My findings so far:
1) The Ev
On Sat, 16 Sep 2017 07:31:18 -0700, alex.jakime...@gmail.com wrote:
> From this discussion https://irclog.perlgeek.de/perl6-dev/2017-09-
> 16#i_15171820
>
> 4) the EvalServer seems to leak memory. it's no longer possible to run
> 'make spectest', even with -Xmx6000m
My findings so far:
1) The Ev
On Thu, 21 Sep 2017 19:50:01 -0700, b...@abrij.org wrote:
>
> Current behavior (don't have a rakudo-j here):
>
> $ perl6-m -e 'class A { has str $.x; method BUILD(:$!x) { } }; say
> A.new(:x).x'
> foo
>
> If r-j now works too, we can move to TESTNEEDED.
Yeah, looks good on rakudo-j, too:
$ ./p
On Sat, 16 Sep 2017 08:46:00 -0700, barto...@gmx.de wrote:
> Here is a simple example:
>
> $ ./perl6-j -e 'try { die "foo" }; say $!.perl; say $!.gist'
> X::AdHoc.new(payload => "foo")
> Died
> in block at -e line 1
It looks like the 'Died' stems from this line:
https://github.com/perl6/nqp/
Here is a simple example:
$ ./perl6-j -e 'try { die "foo" }; say $!.perl; say $!.gist'
X::AdHoc.new(payload => "foo")
Died
in block at -e line 1
$ $ ./perl6-m -e 'try { die "foo" }; say $!.perl; say $!.gist'
X::AdHoc.new(payload => "foo")
foo
in block at -e line 1
The test this ticket was about has been adjusted/removed with
https://github.com/perl6/roast/commit/108337d810
I'm closing this ticket as 'resolved'.
The tests this ticket was about (from RT #69192) have been fixed with
https://github.com/perl6/roast/commit/e4a2c0b589
Since the tests are passing now, I'm closing this ticket as 'resolved'.
On Sat, 21 Nov 2015 01:18:15 -0800, barto...@gmx.de wrote:
> 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?
For the record: These are the two remaining tests
The tests in question where adjusted and unfudged with
https://github.com/perl6/roast/commit/8a351395cd
I'm closing this ticket as 'resolved'.
There was a second attempt at fixing the underlying issue in Rakudo:
https://github.com/rakudo/rakudo/pull/934. The tests in question were adjusted
and unfudged with https://github.com/perl6/roast/pull/187.
Currently there are no longer any fudged tests with this ticket number, so I'm
closing t
On Fri, 22 Apr 2016 12:20:54 -0700, barto...@gmx.de wrote:
> 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
The tests in question have been unfudged with roast commit
https://github.com/perl6/roast/commit/6db316eaae. (This was probably fixed with
merging the 'uncurse' branch.)
The last example from the last comment (using EVAL) works as expected, too:
$ ./perl6-m -e 'say Map.new("a", 42).perl.EVAL'
M
There is no InvalidArgumentException anymore. I've added a test to
S32-hash/perl.6 with commit https://github.com/perl6/roast/commit/bae1108d8f.
I'm closing this ticket as 'resolved'.
This works now. I've added a simple test to S02-names/pseudo.t with roast
commit 7edf26aae4.
$ ./perl6-j -e 'say CORE::.keys'
(SoftRoutine PF_LOCAL &METAOP_REDUCE_XOR &exit Rat Rational Slang &sqrt buf8
$?COMPILATION-ID &nextcallee &infix:<∘> &kv NQPMatchRole &any &sleep-until
SIGTRAP &join &ME
This works now. I've added a simple test to S02-names/pseudo.t with roast
commit 7edf26aae4.
$ ./perl6-j -e 'say CORE::.keys'
(SoftRoutine PF_LOCAL &METAOP_REDUCE_XOR &exit Rat Rational Slang &sqrt buf8
$?COMPILATION-ID &nextcallee &infix:<∘> &kv NQPMatchRole &any &sleep-until
SIGTRAP &join &ME
The test in S02-names/pseudo.t passes on JVM now. I'm closing this ticket as
'resolved'.
The test in S02-names-vars/perl.t is passing now. I'm closing this ticket as
'resolved'.
Those UnwindExceptions are gone now. The tests in S32-num/polymod.t and
integration/advent2011-day23.t are passing again.
I'm closing this ticket as 'resolved'.
This works now (and the test in S02-names-vars/list_array_perl.t is unfudged):
$ ./perl6-j -e 'my $foo = [42 ]; $foo[1] = $foo; say $foo.perl; say
$foo.perl.EVAL'
((my @Array_1924162593) = $[42, @Array_1924162593])
(\Array_532302454 = [[42 Array_532302454]])
I'm closing this ticket as 'resolved'
This problem has been resolved:
$ ./perl6-j -e 'my @array = 0..1; @array[0]:delete; say map { $_ }, @array'
((Any) 1)
The test in S32-array/delete.t is passing on the JVM backend as well. I'm
closing this ticket as 'resolved'.
This seems to be resolved now:
$ ./perl6-j --version
This is Rakudo version 2017.08-104-g76f1d8970 built on JVM
implementing Perl 6.c.
$ ./perl6-j -e 'say (2).combinations(0)'
(())
Since there are tests for this behaviour in S32-list/combinations.t, I'm
closing this ticket as 'resolved' without
On Mon, 20 Mar 2017 01:19:43 -0700, j...@durchholz.org wrote:
> I was wondering how the Unicode consortium might extend this limit, so I
> investigated a bit.
>
> TL;DR
>
> I can confirm that 10 is going to remain the maximum for the
> foreseeable future.
Thanks for sharing your findings!
This issue was about a failing test for too large unicode code points.
#?rakudo.moar todo 'chr max RT #124837'
dies-ok {chr(0x10+1)}, "chr out of range (max)";
Ticket https://rt.perl.org/Ticket/Display.html?id=130914 has more informations,
so I'm closing this one as a duplicate.
I started to add a test or two for this issue, but then I found the following
test in S29-conversions/ord_and_chr.t:
#?rakudo.moar todo 'chr max RT #124837'
dies-ok {chr(0x10+1)}, "chr out of range (max)";
Looking at https://en.wikipedia.org/wiki/Code_point and
http://www.unicode.org/gl
This now works on JVM as well (see rakudo commit c3c86dcf51). The test in
t/05-messages/01-errors.t passes.
$ ./perl6-j -e 'my $x = fail'
Failed
in block at -e line 1
I'm closing this ticket as 'resolved'.
On Fri, 17 Feb 2017 12:41:12 -0800, david.warring wrote:
> 09:38] r: my $r := do 42 with Nil; say $r.perl;
> [09:38] <+camelia> rakudo-moar a162c4: OUTPUT«Empty»
> [09:38] <+camelia> ..rakudo-jvm fb4f16: OUTPUT«slip()»
Just a short comment on this: Camelia runs on an older commit (fb4f16 is fro
I think I know what happens. On MoarVM we call the Perl 6 method 'defined':
https://github.com/perl6/nqp/blob/ac9a66abad13a7fd3d52b22ba533a9f8436ad1ac/src/vm/moar/QAST/QASTOperationsMAST.nqp#L787
On JVM we test for concreteness (like nqp::isconcrete would do):
https://github.com/perl6/nqp/blob/
FWIW that hangs on FreeBSD as well (maybe not too much a surprise, given the
relationship of the OSes).
The test in question is this:
is(("acdbcdbe" ~~ rx:P5/a(?:b|c|d){6,7}?(.)/ && $0), "e", 're_tests 617/1
(801)');
It turns out that the problem is not related to P5, but happens with P6Regex as
well:
r: say ("ddd" ~~ / [ x | d ] **? 3 /)
rakudo-jvm fb4f16: OUTPUT«｢d｣»
..rakudo-moar 637
The test in question does not die anymore on JVM. The test does not pass yet
(its fudged 'todo' for all backends), but it fails the same way as it does on
MoarVM. There is https://rt.perl.org/Ticket/Display.html?id=124660 for that
failure.
I'm closing this ticket as 'resolved'.
On Sat, 14 Jan 2017 03:06:52 -0800, elizabeth wrote:
> Hopefully fixed in 00c3551c86 . Cannot check because building JVM
> backend fails on MacOS.
As discussed on #perl6-dev [1] this didn't fix the issue, unfortunately.
I think, I've found the underlying reason for the breakage. This is a golf o
On Sun, 08 Jan 2017 23:31:11 -0800, barto...@gmx.de wrote:
> Since the new Rakudo::Internals.OneValueIterator is used in infix:
> (Rakudo commit c405f06724) there are four failing tests in
> S03-metaops/zip.t on rakudo-j.
>
> One example of failing code:
>
> $ ./perl6-j -e 'say $(1, 2) Z '
> (((1
A test was added with https://github.com/perl6/roast/commit/90c58ff0eb
I'm closing this ticket as 'resolved'.
On Sun, 08 Jan 2017 05:11:03 -0800, barto...@gmx.de wrote:
> With rakudo commit 3c52aa096c Seq got it's own join method. For some
> reason that changed the behaviour of 'redo' in 'grep'
Also, next/redo in grep die on rakudo-j when using the new join method:
$ ./perl6-j -e 'say (1..4).grep({next i
On Tue, 13 Sep 2016 12:42:03 -0700, barto...@gmx.de wrote:
> All code examples from above are running fine now.
>
> Instead there are four skipped tests in S32-array/adverbs.t which die
> because the wrong multi postcircumfix:<[ ]> is selected.
>
> I'll change the subject of this ticket and leave
Those tests are passing (again). I'm closing this ticket as 'resolved'.
The tests are passing again. I'm closing this ticket.
On Sat, 31 Dec 2016 11:04:34 -0800, elizabeth wrote:
> > There are many test failures for rakudo-j because
> > X::Method::NotFound is returned instead of X::Assignment::RO.
>
> What is the method that isn’t found? Maybe we need to add it for the
> JVM ?
I suspect the changes from https://github.
Unfortunately commit 8d35951 breaks the build on JVM. It dies during stage
parse with
Error while compiling, type X::Parameter::InvalidType
suggestions: ()
typename: Uni
at line 32953, near " $uni) { "
in panic (gen/jvm/stage2/NQPHLL.nqp:348)
[...]
Type Uni is not usable with rakudo-j:
On Tue, 18 Oct 2016 08:39:21 -0700, barto...@gmx.de wrote:
>
> Again, for the records: lizmat++ put in a bandaid for rakudo-j with
> Rakudo commit 666128fc6e. The tests from S32-list/head.t run fine, but
> the underlying problem is still there.
The bandaid was remove recently (Rakudo commit e8f93
On Fri, 11 Nov 2016 08:57:19 -0800, c...@zoffix.com wrote:
> On Tue, 05 Jul 2016 08:34:51 -0700, zef...@fysh.org wrote:
> > But if the content is non-numeric only by having diacritics on the
> > digits,
> > the coercion produces a bad result:
> >
> > > "34\x[308]5".Int
> > 3
>
> Thanks for the rep
1 - 100 of 755 matches
Mail list logo
