Hi,

In message "[ruby-talk:19713] Re: Why not?: Assigning to self"
    on 01/08/15, Ned Konz <ned / bike-nomad.com> writes:

|I don't see that introducing become() (if it could be done without affecting 
|other parts of the language) would hurt, and it would help in those 
|(admittedly uncommon) cases where it's warranted.

Unfortunately, many internal assume the type (or class) of internal
object remain unchanged, so that "become" can crash the interpreter
and it's hard to make it "become" safe.  I'm not sure it's worthy.
I feel rather negative.

							matz.