Skip Menu |
Report information
Id: 131722
Status: new
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: alex.jakimenko [at] gmail.com
Cc:
AdminCc:

Severity: (no value)
Tag: (no value)
Platform: (no value)
Patch Status: (no value)
VM: (no value)



Subject: [REGRESSION]? Map and containerization (my %m := Map.new(‘a’, ‘X’); %m<a> = 42)
Code: my %m := Map.new(<a X b Y>); %m<a> = 42; say %m.perl Result (2015.12~HEAD): Map.new((:a(42),:b("Y"))) Code: my %m := Map.new(‘a’, ‘X’, ‘b’, ‘Y’); %m<a> = 42; say %m.perl Result (2015.12 ~ 2016.06): Map.new((:a(42),:b("Y"))) Result (2016.07.1 ~ 2017.05): Cannot modify an immutable Str in block <unit> at /tmp/8nf6dnM_9C line 2 Result (2017.06 ~ HEAD(05c255c)): Cannot modify an immutable Str (X) in block <unit> at /tmp/8nf6dnM_9C line 2 The significant change happened after https://github.com/rakudo/rakudo/commit/de5d9e70cbfe678d2371d284e9384f53aba1eb94 I'm not sure what the ideal behavior should be, I'm just pointing out the thing. IRC log: https://irclog.perlgeek.de/perl6/2017-07-09#i_14846532 Another interesting point: Code: my %m := Map.new(<a X b Y>); say %m.perl Result: Map.new((:a("X"),:b("Y"))) Code: my %m := Map.new(‘a’, ‘X’, ‘b’, ‘Y’); say %m.perl Result: Map.new((:a("X"),:b("Y"))) If their .perl is identical, I guess they should behave identically too.
Download (untitled) / with headers
text/plain 282b
There was an email reply to this ticket which for some reason is missing. The issue was temporarily-fixed with a workaround, which would need to be removed to detect if proper fix is fixing the issue: https://github.com/rakudo/rakudo/commit/4894a75d001159fd68ea9d840d0c227a64427b4e


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org