On Thursday, October 17, 2013 18:50:25 Dicebot wrote:
> Well, yeah. it is memory safe but you can't slice a string and be
> sure its value won't change silently - comparable semantical
> safety disaster IMHO.

Yeah. You have to be concerned about whether the values change, which makes 
the string situation considerably worse. But you have to be careful with the 
term "safe," because around here that almost always means memory safety.

- Jonathan M Davis

Reply via email to