Hi,

2009/7/9 Run Paint Run Run <redmine / ruby-lang.org>:
> Bug #1747: Immediate Values Can be Frozen
> http://redmine.ruby-lang.org/issues/show/1747
>
> Author: Run Paint Run Run
> Status: Open, Priority: Normal
> Category: core
> ruby -v: ruby 1.9.2dev (2009-07-08 trunk 23995) [i686-linux]
>
> On 1.8 you couldn't freeze an immediate. On 1.9 you can. Presumably this is a bug.
>
>  $ ruby -ve 'a=true;a.freeze;p a.frozen?'
>  ruby 1.9.2dev (2009-07-08 trunk 23995) [i686-linux]
>  true
>
>  $ ruby8 -ve 'a=true;a.freeze;p a.frozen?'
>  ruby 1.8.8dev (2009-07-01) [i686-linux]
>  false


It seems to be an intentional change for the following use case:

  # http://nov.tdiary.net/20071215.html#p02 (In Japanese)
  CONST2 = ["hoge", 1].freeze
  CONST2.each(&:freeze).all?(&:frozen?) #=> false (expected true)

I have no idea whether the the rationale is sensible or not.
If the compatibility can be ignored, it would be more reasonable that
all immediate values are frozen as a default.

-- 
Yusuke ENDOH <mame / tsg.ne.jp>