I bisected moarvm manually to
https://github.com/MoarVM/MoarVM/commit/a6abd3c6654413d2230470dbaa82b7b3a2b05762
On 2017-08-30 19:09:18, alex.jakime...@gmail.com wrote:
> Bisected to
>
https://github.com/rakudo/rakudo/commit/51b63bf9f0d0594687908f0756774f29cde39c1f
>
> On 2017-08-25 18:56:37,
Bisected to
https://github.com/rakudo/rakudo/commit/51b63bf9f0d0594687908f0756774f29cde39c1f
On 2017-08-25 18:56:37, alex.jakime...@gmail.com wrote:
> The input file for this problem is ≈15 MB so please bear with external
> link:
> https://files.progarm.org/golfed.gz (1.6 MB compressed)
>
>
# New Ticket Created by Stephen Roe
# Please include the string: [perl #131997]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131997 >
This is Rakudo version 2017.04.3 built on MoarVM version 2017.04-53-g66c6dda
implementing
# New Ticket Created by Sylvain Colinet
# Please include the string: [perl #131998]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131998 >
m: class A {;}; my A $a .= new(:name:); # lta error ?
rakudo-moar 3e1382: OUTPUT:
Looks like this bug affects subroutines too:
m: say ~~ Callable
rakudo-moar 3e1382: OUTPUT: «False»
m: say [0,1,2,Any].grep()
rakudo-moar 3e1382: OUTPUT: «Cannot resolve caller
ACCEPTS(Sub+{}: Int);
Brian S. Julin via RT wrote:
>For example "Foo^".."Bar" and "Foo"^.."Bar" would put out the same WHICH.
Yes, and that's a bigger problem. In general Rakudo's .WHICH methods
suffer this sort of problem when incorporating the .WHICH values of
subobjects. See [perl #128943] (Set, and in which I
# New Ticket Created by Александр Кирюхин
# Please include the string: [perl #131996]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131996 >
This one is tough.