[ruby-core:98815] [Ruby master Feature#15627] Appearance of custom singleton classes

Issue #15627 has been updated by ParadoxV5 (塀麦髪麦硲溌鳩竇、笂ケ 笵・).


That being said,

Why does `TrueClass`, `FalseClass` and `NilClass` classes in `Object` instead of just `singleton_class` of `true`, `false` and `nil` repectively?

If it窶冱 for backwards compatibility, remember that with major updates (e.g. Ruby 3.0) we don窶冲 need to guarantee backward-compatibility (Ruby 3窶冱 being changes to how keyword arguments are parsed).

(`true`, `false` and `nil` are more like pseudo-*constants* compared to other pseudo-variables (`self`, `__FILE__`, `__LINE__`))

----------------------------------------
Feature #15627: Appearance of custom singleton classes
https://bugs.ruby-lang.org/issues/15627#change-86177

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
----------------------------------------
When I have a singleton class `AClass` of an instance `a` of a custom class `A`,


```ruby
class A; end
a = A.new
AClass = a.singleton_class
```

i) even though the singleton class of `nil`, `false`, and `true` are referred to by their assigned constant names, the singleton class `AClass` of `a` is not:

```ruby
nil.singleton_class #=> NilClass
false.singleton_class #=> FalseClass
true.singleton_class #=> TrueClass
a.singleton_class #=> #<Class:#<A:0x00007fda832a7eb0>>
```

ii) even though the singleton class of `nil`, `false`, and `true` appear as their class, the singleton class `AClass` of `a` does not:

```ruby
nil.class #=> NilClass
false.class #=> FalseClass
true.class #=> TrueClass
a.class #=> A
```

This contrast between `nil`, `false`, and `true` on the one hand and `a` on the other is confusing. I am actually not sure if this is intended behaviour It may be related to
* https://bugs.ruby-lang.org/issues/15608
* https://bugs.ruby-lang.org/issues/14895

I expect `AClass` to behave the same as with `NilClass`, `FalseClass`, and `TrueClass`. I expect:

```ruby
a.singleton_class #=> AClass
a.class #=> AClass
```

If the current behaviour is intended, I would like this to become a feature request.



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

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>