sferik (Erik Michaels-Ober)
- Login: sferik
- Email: sferik@gmail.com
- Registered on: 02/28/2011
- Last sign in: 09/10/2015
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 1 | 2 | 3 |
Activity
03/19/2015
- 02:11 PM Ruby master Bug #10984: Hash#contain? to check whether hash contains other hash
- I agree that `#include?` is a more consistent and appropriate name for this method. I would prefer to see that change...
11/16/2014
- 04:38 AM Ruby master Feature #10510: Remove REXML instead of patching it
- I believe semantic versioning prevents doing this until Ruby 3 is released (many years from now) but I agree that thi...
02/21/2014
- 09:11 PM Ruby master Feature #9549 (Rejected): Improvements to Time::strptime
- I opened [a pull request on GitHub](https://github.com/ruby/ruby/pull/540) a few days ago but wanted to open a parall...
11/21/2013
- 09:06 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
- =begin
> The opposite of "zero?" is not "nonzero?" but "notzero?". If the method's name was "notzero?", one could ca... - 05:07 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
- =begin
I'm not proposing a change to the semantics of Ruby; I'm proposing a fix to an inconsistency.
The vast majori...
11/19/2013
- 10:32 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
- I did not remove that example, I just moved it under the documentation for Numeric#nonzero.
- 03:31 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
- How would you feel if Numeric#zero? returned self (0) or nil?
Your description of the semantics of the question mark... - 03:12 AM Ruby master Feature #9123 (Assigned): Make Numeric#nonzero? behavior consistent with Numeric#zero?
- Numeric#zero? returns true or false, while Numeric#nonzero? returns self or nil.
I've written a patch that fixes t...
12/04/2012
- 04:35 PM Ruby master Feature #7414: Now that const_get supports "Foo::Bar" syntax, so should const_defined?.
- I also noticed this inconsistency. It seems very odd to have different behavior for Module#const_get and Module#const...
05/12/2011
- 03:13 AM Ruby master Bug #4651: Bus Error using continuation on x86_64-darwin11.0.0 (Lion)
- Just to be clear, this is still an issue on Ruby 1.9.2-head but it's fixed in trunk (1.9.3). Maybe I'm using the wron...
Also available in: Atom