Issue #21556 has been updated by Phalado (Raphael Cordeiro). nobu (Nobuyoshi Nakada) wrote in #note-1:
Phalado (Raphael Cordeiro) wrote:
Sometimes we need to check for an exact `true` or `false` value. This can be a string or a boolean value.
For what situation, and why mixing strings and `true`/`false`? It sounds like depending on applications/libraries.
Data received on requests and JSON conversion. It's not unusual that a Boolean is converted to a String, or users end up filling in as a String instead of a Boolean. ---------------------------------------- Feature #21556: Add true? and false? methods to NilClass, TrueClass, FalseClass, and String https://bugs.ruby-lang.org/issues/21556#change-114473 * Author: Phalado (Raphael Cordeiro) * Status: Feedback ---------------------------------------- Sometimes we need to check for an exact `true` or `false` value. This can be a string or a boolean value. Usually, what I do to solve this is something like `value.to_s == true`, this way covering for strings, booleans, and nil values. The idea of these new methods is to check for the exact value, being it a String, a Boolean, or even a Nil value. This is the result obtained: ``` ruby # String 'true'.true? # true 'false'.true? # false ''.true? # false 'true'.false? # false 'false'.false? # true ''.false? # false # Boolean true.true? # true true.false? # false false.true? # false false.false? # true # Nil nil.true? # false nil.false? # false ``` -- https://bugs.ruby-lang.org/