Project

General

Profile

Actions
Copy link

Bug #11063

closed

Special singleton class should return true for singleton_class? test

Bug #11063: Special singleton class should return true for singleton_class? test

Added by rbjl (Jan Lelis) about 11 years ago. Updated over 4 years ago.

Status:
Rejected
Assignee:
-
Target version:
-
ruby -v:
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
Backport:
2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
[ruby-core:<unknown>]
Tags:
core, patch, maybenotbug

Description

This seems wrong (or at least inconsistent):

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

Files

special_singletons.patch (1.16 KB) special_singletons.patch rbjl (Jan Lelis), 04/12/2015 07:50 PM

Related issues 2 (0 open — 2 closed)

Related to Ruby - Bug #11064: #singleton_methods for objects with special singleton_class returns an empty arrayClosedActions
Related to Ruby - Feature #12084: `Class#instance`ClosedActions

Updated by Eregon (Benoit Daloze) over 4 years ago Actions
Copy link
 #1

  • Related to Bug #11064: #singleton_methods for objects with special singleton_class returns an empty array added

Updated by Eregon (Benoit Daloze) over 4 years ago Actions
Copy link
 #2

Updated by Eregon (Benoit Daloze) over 4 years ago Actions
Copy link
 #3 [ruby-core:107845]

Changing this would cause the reverse inconsistency:

false.class.singleton_class? #=> would be true, but .class.singleton_class? should always be false

The only real fix would be to have separate class and singleton_class for nil/false/true, but it's unclear if that's worth it.

Updated by matz (Yukihiro Matsumoto) over 4 years ago Actions
Copy link
 #4 [ruby-core:107951]

  • Status changed from Open to Rejected

This inconsistency does not have any actual drawback, so we keep the current behavior.

Matz.

Actions
Copy link

Also available in: PDF Atom