[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

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 it open to collect those weird errors about wrong multi candidates

[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

And now a lot of tests from roast exploded with "Expected a native int argument for '$a'" after this commit introduced two uses of postfix:<++> and postfix:<--> in lib/Test.pm6: https://github.com/rakudo/rakudo/commit/ffb5789f7eef1157c7556897c4805569df4f7aa4 Modifying the two relevant lines

[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

I found another strange failure which dies the same way. The error happens in S32-list/combinations.t and can be golfed down to this: $ ./perl6-j -e 'say (1).combinations(0..1); say ().combinations' (() (1)) Expected a native int argument for '$a' Like my original report this happens while

[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

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

[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

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

Re: [perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

Reverted for JVM in d9b19da , but I think this warrants further research.: > On 11 May 2016, at 07:44, Christian Bartolomaeus (via RT) > wrote: > > # New Ticket Created by Christian Bartolomaeus > # Please include the string: [perl #128123] > # in the subject

Re: [perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

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?? Liz > On 11 May 2016, at 07:44, Christian Bartolomaeus (via RT) > wrote: > > # New Ticket Created by

[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

# New Ticket Created by Christian Bartolomaeus # Please include the string: [perl #128123] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128123 > The following code from S03-metaops/hyper.t dies on rakudo-j: $ perl6-j -e