From: ko1@...
Date: 2014-09-10T08:30:37+00:00
Subject: [ruby-core:64923] [ruby-trunk - Feature #8923] Frozen nil/true/false

Issue #8923 has been updated by Koichi Sasada.


Hans Mackowiak wrote:
> i am unsure about toally freeze them ... some might extend/include some "Boolean" module into true/false or the TrueClass/FalseClass to specially check if a value is only true or false
> 
> i dont know if freezing this objects would break such a thing ...

```ruby
p true.frozen? #=> true
module Boolean; end
class TrueClass
  include Boolean
end
p true.kind_of?(Boolean) #=> true
```

Not freeze TrueClass, but freeze true object.


----------------------------------------
Feature #8923: Frozen nil/true/false
https://bugs.ruby-lang.org/issues/8923#change-48786

* Author: Koichi Sasada
* Status: Open
* Priority: Normal
* Assignee: Yukihiro Matsumoto
* Category: core
* Target version: current: 2.2.0
----------------------------------------
Related to [Feature #8906]

We already froze `Integer`, `Float`. `Symbol`s soon (now working).

How about to freeze `nil`, `true` and `false`, too?

 # frozen ruby? "Ruby"f?




-- 
https://bugs.ruby-lang.org/