From: nobu@... Date: 2018-04-06T00:26:19+00:00 Subject: [ruby-core:86464] [Ruby trunk Feature#14666][Rejected] nil.any?{} should return false Issue #14666 has been updated by nobu (Nobuyoshi Nakada). Description updated Status changed from Open to Rejected `any?`, `all?`, and the family can be defined only on container objects from the meanings. `nil` is not a container object. ---------------------------------------- Feature #14666: nil.any?{} should return false https://bugs.ruby-lang.org/issues/14666#change-71399 * Author: eike.rb (Eike Dierks) * Status: Rejected * Priority: Normal * Assignee: * Target version: ---------------------------------------- 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 existence quantors are well defined on `nil`. So `nil.any?` should always return `false` I know this might make more sense to return `NoMethodError` But in the end `nil` is an object, it's not a null pointer exception any more We can actually talk with `nil`. Back in the objc days talking to `nil` would always return `nil`, Im not sure what happens if `nil` answers `false` to `any?` (currently it throws an exception, code should not depend on that) I believe `nil` is a deep concept, and ruby got far ahead with the Nil class I'd like to suggest that `nil.any?{}` should return false -- https://bugs.ruby-lang.org/ Unsubscribe: