# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #125289]
# in the subject line of all future correspondence about this issue.
# <URL: https://rt.perl.org/Ticket/Display.html?id=125289 >
<zostay> m: my %h = a => [a => 1], b => [b => 1, b => 2]; %h.perl.say;
%h.perl.EVAL;
<camelia> rakudo-moar c2a57e: OUTPUT«{:a([:a(1)]), :b([:b(1),
:b(2)])}<>Type check failed in binding op; expected 'Any' but got
'Mu' [...]
<lizmat> m: {:a([:a(1)])} # shorter golf of zostay++ problem
<camelia> rakudo-moar c2a57e: OUTPUT«Type check failed in binding op;
expected 'Any' but got 'Mu' [...]
<lizmat> m: [:a(1)] # even shorterer golf
<camelia> rakudo-moar c2a57e: OUTPUT«Type check failed in binding op;
expected 'Any' but got 'Mu' [...]
<lizmat> zostay: care to rakudobug this ? At least, the .perl output
should be fixed to allow roundtripping again
<lizmat> m: [:a] # shorterest golf
<camelia> rakudo-moar c2a57e: OUTPUT«Type check failed in binding op;
expected 'Any' but got 'Mu' [...]
<lizmat> m: [:a,].perl.say # works
<camelia> rakudo-moar c2a57e: OUTPUT«[:a]»
<masak> I guess `[:a]` should be an array of one Pair, too.
<lizmat> m: [a=> 1].perl.say # that was the intent
<camelia> rakudo-moar c2a57e: OUTPUT«[:a(1)]»
<camelia> rakudo-moar c2a57e: OUTPUT«[:a(1)]»
<lizmat> m: [a=> True].perl.say # closer to the thing
<camelia> rakudo-moar c2a57e: OUTPUT«[:a]»
<lizmat> m: [a=> True].perl.EVAL # not roundtripping
<camelia> rakudo-moar c2a57e: OUTPUT«Type check failed in binding op;
expected 'Any' but got 'Mu' [...]
<lizmat> m: [(:a)].perl.say # does work
<camelia> rakudo-moar c2a57e: OUTPUT«[:a]»
<masak> yeah, something is wrong there.
* masak submits rakudobug
<lizmat> note that the error occurs in from
src/gen/m-CORE.setting:23160
(/Users/liz/Github/rakudo.moar/install/share/perl6/runtime/./CORE.setting.moarvm:METAOP_REDUCE_LEFT:17)
<lizmat> METAOP_REDUCE_LEFT ???
<masak> METAOP_REDUCE_LEFT could be because someone did [~] somewhere
