"Mehrdad" <[email protected]> wrote in message news:[email protected]... > Related suggestion: All methods that return /new/ strings should return > *mutable* arrays. There's really no reason (that I can think of) to not do > this: if you see something returning a mutable array, you _know_ it's a > new array (unless otherwise documented), so you _know_ it's safe to cast > it to immutable if needed. It doesn't work the other way around, though.
Since a few days ago, mutable strings returned from strongly pure functions can be implicitly converted to immutable ones, so a cast won't be needed any more.
