Safety, undefined behavior, @safe, @trusted
Walter Bright
newshound1 at digitalmars.com
Thu Nov 5 19:32:27 PST 2009
Steven Schveighoffer wrote:
> However, I'll let it go, I don't know the ramifications since allocating
> immutable objects is a rare occurrence, and I'm not sure how it will be
> done. I am also not sure how solid a use case this is (allocating an
> object, then manipulating it via methods before changing it to immutable).
I don't have any solid history with this, it's just my opinion that the
right place for it is at the function level. Experience may show your
idea to be better, but it's easier to move in that direction later than
to try and turn off support for unsafeness at the statement level.
More information about the Digitalmars-d
mailing list