[ruby-core:91640] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[ruby-core:91640] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[sawadatsuyoshi]

Issue #15627 has been reported by sawa (Tsuyoshi Sawada).

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/

[ruby-core:91645] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[shevegen]

Issue #15627 has been updated by shevegen (Robert A. Heiler).


I sort of agree.

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/

[ruby-core:91646] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[eregontp]

Issue #15627 has been updated by Eregon (Benoit Daloze).


`singleton_class` and `class` are different by design.
They are only the same for `true`, `false` and `nil`.

Having the singleton class get named when assigning it to a constant sounds like a possible feature.
Although it doesn't seem common to assign a singleton class to a constant.

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/

[ruby-core:91657] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[nobu]

Issue #15627 has been updated by nobu (Nobuyoshi Nakada).


At first, as no syntax to name a singleton class like ordinary classes/modules, singleton classes cannot have a name.
And name-by-assignment is a “best effort” (or “better than nothing”).

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/

[ruby-core:91729] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[mame]

Issue #15627 has been updated by mame (Yusuke Endoh).


Rather, it looks a bug that `#singleton_class` returns a non-singleton class:

```
p Object.new.singleton_class.singleton_class? #=> true

p true .singleton_class.singleton_class? #=> false
p false.singleton_class.singleton_class? #=> false
p nil  .singleton_class.singleton_class? #=> false

1.singleton_class #=> can't define singleton (TypeError)
```

It looks reasonable to raise an exception like `1.singleton_class`.  (But I'm unsure if it is worth enough to break compatibility.)

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/

[ruby-core:91735] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[hanmac]

Issue #15627 has been updated by Hanmac (Hans Mackowiak).


@mame it is by design that true, false and nil has their class work as singleton class so you can do:

```ruby

def true.bla
  # something
end
```

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/

[ruby-core:91737] [Ruby trunk Bug#15627] Appearance of custom singleton classes

[mame]

Issue #15627 has been updated by mame (Yusuke Endoh).


Wow.

```
def true.foo; end
p TrueClass.instance_methods.include?(:foo) #=> true
```

I didn't know, thanks.  I have used Ruby for fifteen years, but Ruby still brings fresh surprise to me.

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

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
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/