[ruby-core:24258] [Bug #1747] Immediate Values Can be Frozen

Issue #1747 has been updated by Run Paint Run Run.


Defining instance methods on Fixnum instances seems a particularly contrived case, even for ruby-core. ;-) The troubled soul wishing to engage in such hackery could surely stretch as far as using a Struct to wrap his annotated numerals? Note that freezing immediates does not imply freezing their classes; singleton methods could still be added if desired. 

In addition, it makes little conceptual sense to freeze a value that is frozen by definition. This is especially obvious when you consider that because immediates can't be dup'd, they can never be thawed. The abstraction is broken.

Triskadekaphobiacs are presumably upset that, although 13.untrust appears to succeed and reinforce their beliefs, the state doesn't stick; 13.untrusted? subsequently returns false. Similarly, logicians and cynics alike must, respectively, rejoice and despair that `true.untrust.untrusted?` is perpetually false.

It is irrational in equal measures to #freeze an immediate as it is to #dup it; to #taint truth (`true`) as it is to assign to it; to #trust the unknowable (nil) as it is to #untrust it.

If methods don't make a sense for an object, they shouldn't appear to work. :-)
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1747

----------------------------------------
http://redmine.ruby-lang.org