From: hi@... Date: 2016-06-23T02:10:12+00:00 Subject: [ruby-core:76109] [Ruby trunk Feature#12515] Create "Boolean" superclass of TrueClass / FalseClass Issue #12515 has been updated by Olivier Lacan. Shyouhei Urabe wrote: > You failed here. This admittedly could be lost in translation but I don't think this a very nice way to react to Loren's proposal. He didn't fail here. He just proposed something. You either think it's a good idea or a bad idea. I wish you provide your opinion a bit more kindly. > https://github.com/search?l=ruby&q=%22class+Boolean%22&type=Code > https://rubygems.org/search?query=Boolean > > I guess it's too late. I can change the search query to `Integer` and provide similarly dubious reasons why Integer would be bad idea: https://github.com/search?l=ruby&q=%22class+Integer%22&type=Code https://rubygems.org/search?query=Integer I don't think this is very solid counterpoint. ---------------------------------------- Feature #12515: Create "Boolean" superclass of TrueClass / FalseClass https://bugs.ruby-lang.org/issues/12515#change-59314 * Author: Loren Segal * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Since Ruby 2.4 is unifying Bignum/Fixnum into Integer (https://bugs.ruby-lang.org/issues/12005), it seems reasonable to do something similar for TrueClass / FalseClass, and create a proper Boolean hierarchy. The implementation would be fairly straightforward and should be back compat unless someone already has a "Boolean" class at toplevel out there. Given the compatibility implications of Integer, this Boolean proposal is even less intrusive. Sample implementation: ~~~ class Boolean < BasicObject; end class TrueClass < Boolean; end class FalseClass < Boolean; end ~~~ -- https://bugs.ruby-lang.org/ Unsubscribe: