I fully aggree with all the commenters. It boils down to if nil should be Enumerable. Obviously it should be not. because nil is special. But then nil means "not in list" or the empty list or the not existing list? I know this ...eike.rb (Eike Dierks)
Hi everyone at ruby/trunk I encountered `nil.any?` ``` undefined method `any?' for nil:NilClass (NoMethodError) ``` I fully agree with all of yours, that `nil` should be kept slim. But than, on the other hand, the existen...eike.rb (Eike Dierks)
Dear friends at ruby I'd like to suggest a new error for ruby-core: LogicError That error should be thrown upon operations that are detected to be illogic or impossible by semantics. I believe that this could improve the error me...eike.rb (Eike Dierks)
This must have been discussed before, please reassigned and close this one. I want to propose an extension to the ruby core api: - add #step(n) for Enumerable, Enumerator - coerce the step() api across all the api (see Numeric#step...eike.rb (Eike Dierks)
I'd like to suggest an extension to the signature of stdlib Forwardable#def_instance_delegator currently (ruby 2.3.3) it is declared as: ```ruby def_instance_delegator(accessor, method, ali = method) ``` I'd like to add a ni...eike.rb (Eike Dierks)
I'd like to suggest to enhance the interface of stdlib/logger The #new method should allow for an option to set the log level: ~~~ruby Logger#new(logdev, level:'WARN') ~~~ As with ruby 2.4 there is no provision to set the log...eike.rb (Eike Dierks)
ruby crashed - never seen that before - should never happen - looks serious to me I'm using ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15] from macports I was running rails in dev mode. The bug happened while rel...eike.rb (Eike Dierks)
I am well aware that ruby is not typed (and so for a good reason) But sometimes it makes sense to check the types (or values) of arguments upfront. (It actually helps to narrow down your arguments to the known) I'd like to suggest...eike.rb (Eike Dierks)
I'd like to suggest a new syntactic feature. There should be an operator `!==` which should just return the negation of the `===` operator ### aka: ```ruby def !==(other) ! (self === other) end ``` ### Rationale: T...eike.rb (Eike Dierks)
OK, that change would break the spec. I do understand that breaking the spec something that we rarely want to do. I found a workaround: ArgumentError.new([arg]) # wrap arg in Array to give a better error message when arg is nil ...eike.rb (Eike Dierks)