# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #126220]
# in the subject line of all future correspondence about this issue.
# <URL: https://rt.perl.org/Ticket/Display.html?id=126220 >
Code:
++.++
Result:
Parameter '$a' expected a writable container, but got Int value
in block <unit> at ./test2.pl:2
There is no $a in user code, so it should not be mentioned.
“$a” is mentioned because:
.say for &postfix:<++>.candidates
Result:
sub postfix:<++> (Mu:D $a is rw) { #`(Sub|169376128) ... }
sub postfix:<++> (Mu:U $a is rw) { #`(Sub|169376224) ... }
sub postfix:<++> (Bool:U $a is rw) { #`(Sub|169375744) ... }
sub postfix:<++> (Int:D $a is rw) { #`(Sub|169375840) ... }
sub postfix:<++> (int $a is rw) { #`(Sub|169375552) ... }
sub postfix:<++> (Num:D $a is rw) { #`(Sub|169375936) ... }
sub postfix:<++> (Num:U $a is rw) { #`(Sub|169376032) ... }
sub postfix:<++> (num $a is rw) { #`(Sub|169375648) ... }
<FROGGS> AlexDaniel: imagine you have a $a near that bit of code and waste
hours :o)
Indeed!
Same thing with -- and possibly other ops.
Perhaps there is some universal solution that will fix other problems like
this?
<jnthn> What is a bit bothersome is that we don't report that we're *in*
CORE.setting
<jnthn> So the backtrace makes it look like it could be in your own code
<FROGGS> jnthn: don't we hide that information on purpose?
<jnthn> FROGGS: Yeah, 'cus in other times it's annoying to do otherwise :P
<jnthn> Can't win! :)
