From: "alexeymuranov (Alexey Muranov)" <redmine@...> Date: 2013-11-21T15:28:15+09:00 Subject: [ruby-core:58458] [ruby-trunk - Feature #9123] Make Numeric#nonzero? behavior consistent with Numeric#zero? Issue #9123 has been updated by alexeymuranov (Alexey Muranov). BertramScharpf (Bertram Scharpf) wrote: > The opposite of "zero?" is not "nonzero?" but "notzero?". If the method's > name was "notzero?", one could call it an inconsistency. "nonzero?" is > not a yes-no-question. "Nonzero" is an adjective, opposite of the adjective "zero". "Not zero" is the negation of "zero", so essentially the same thing as "nonzero", but not a single word. ---------------------------------------- Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero? https://bugs.ruby-lang.org/issues/9123#change-43053 Author: sferik (Erik Michaels-Ober) Status: Open Priority: Normal Assignee: Category: Target version: Numeric#zero? returns true or false, while Numeric#nonzero? returns self or nil. I've written a patch that fixes this inconsistency and adds a Numeric#nonzero (non-predicate) method that returns self or nil for chaining comparisons. I'd like for this to be included in Ruby 2.1.0. https://github.com/ruby/ruby/pull/452.patch -- http://bugs.ruby-lang.org/