I concur. The language shouldn't bend over backwards to accommodate bad habits.
On 6/15/16, Elizabeth Mattijsen <[email protected]> wrote: >> On 15 Jun 2016, at 00:38, Alex Jakimenko (via RT) >> <[email protected]> wrote: >> >> # New Ticket Created by Alex Jakimenko >> # Please include the string: [perl #128402] >> # in the subject line of all future correspondence about this issue. >> # <URL: https://rt.perl.org/Ticket/Display.html?id=128402 > >> >> >> Code: >> my $x := 42; >> my $a = 4 + 8; $x = 24; my $b = 15 + 16; >> >> >> Result: >> Cannot assign to an immutable value >> in block <unit> at foo.p6 line 2 >> >> >> Line 2, right, but where exactly? Surely it can also print the cursor >> position or something. > > We don’t have the $/.CURSOR around at runtime. So in order to show where it > happened in the line, one would have to also put that info in the opcodes. > That feels like bloat to me. > > Workaround: put the assignments on different lines :-) > > > Liz
