[Issue 5059] String assignment in foreach loop breaks immutability

2011-07-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5059 Andrej Mitrovic andrej.mitrov...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 5059] String assignment in foreach loop breaks immutability

2011-05-24 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5059 --- Comment #3 from Steven Schveighoffer schvei...@yahoo.com 2011-05-24 14:44:26 PDT --- I think the better solution is to change it to const(char)[]. This better reflects that the data may be changing between iterations. If you are not

[Issue 5059] String assignment in foreach loop breaks immutability

2011-05-24 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5059 --- Comment #5 from Steven Schveighoffer schvei...@yahoo.com 2011-05-24 15:28:28 PDT --- I completely misunderstood the problem here, I thought the string was being directly returned in the opApply delegate, not a Key object. Yes, I agree,

[Issue 5059] String assignment in foreach loop breaks immutability

2011-05-24 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5059 --- Comment #6 from Andrej Mitrovic andrej.mitrov...@gmail.com 2011-05-24 16:53:41 PDT --- Yeah from a quick glance at the registry module it does seem a little fishy overall. __gshared variables, ASCII-only WinAPI calls (what if the registry

[Issue 5059] String assignment in foreach loop breaks immutability

2011-05-24 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5059 --- Comment #8 from Steven Schveighoffer schvei...@yahoo.com 2011-05-24 17:08:24 PDT --- I think this was a D1 module casted to D2 to get it to compile :) Probably would be better served reimplemented, but obviously someone would have to

[Issue 5059] String assignment in foreach loop breaks immutability

2011-04-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5059 Jesse Phillips jesse.k.phillip...@gmail.com changed: What|Removed |Added CC|