[#24105] [Bug #1711] Marshal Failing to Round-Trip Certain Recurisve Data Structures — Run Paint Run Run <redmine@...>

Bug #1711: Marshal Failing to Round-Trip Certain Recurisve Data Structures

9 messages 2009/07/01

[#24116] [Bug #1715] Numeric#arg for NaN is Inconsistent Across Versions — Run Paint Run Run <redmine@...>

Bug #1715: Numeric#arg for NaN is Inconsistent Across Versions

10 messages 2009/07/02

[#24240] [Bug #1755] IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8 — Run Paint Run Run <redmine@...>

Bug #1755: IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8

8 messages 2009/07/09

[#24321] [Bug #1773] Gem path doesn't honor user gem? — Lin Jen-Shin <redmine@...>

Bug #1773: Gem path doesn't honor user gem?

12 messages 2009/07/14

[#24390] [Feature #1784] More encoding (Big5 series) support? — Lin Jen-Shin <redmine@...>

Feature #1784: More encoding (Big5 series) support?

12 messages 2009/07/16

[#24467] Re: [ruby-cvs:31226] Ruby:r24008 (ruby_1_8_6): Removed private on to_date and to_datetime. — Urabe Shyouhei <shyouhei@...>

Hello.

10 messages 2009/07/21

[#24472] [Feature #1800] rubygems can replace system executable files — Kazuhiro NISHIYAMA <redmine@...>

Feature #1800: rubygems can replace system executable files

13 messages 2009/07/21

[#24530] [Feature #1811] Default BasicSocket.do_not_reverse_lookup to true — Roger Pack <redmine@...>

Feature #1811: Default BasicSocket.do_not_reverse_lookup to true

9 messages 2009/07/23

[#24624] [Bug #1844] Immediates Should Not Respond to :dup — Run Paint Run Run <redmine@...>

Bug #1844: Immediates Should Not Respond to :dup

15 messages 2009/07/30

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

From: Yusuke ENDOH <mame@...>
Date: 2009-07-09 04:15:40 UTC
List: ruby-core #24228
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>

In This Thread