From: "Eregon (Benoit Daloze)" <redmine@...>
Date: 2013-11-23T00:54:14+09:00
Subject: [ruby-core:58504] [ruby-trunk - Feature #9123] Make	Numeric#nonzero? behavior consistent with Numeric#zero?


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


mame (Yusuke Endoh) wrote:
> By the way, I investigated the early history of nonzero?.

Very interesting, thank you a lot for reporting it!


Personally I do sometimes use #nonzero? semantics when I want an Integer, but another value if it happens to be 0.
I think it complements the fact any Integer is truthy in Ruby.
----------------------------------------
Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
https://bugs.ruby-lang.org/issues/9123#change-43089

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/