From: "knu (Akinori MUSHA)" <noreply@...>
Date: 2021-09-11T13:04:17+00:00
Subject: [ruby-core:105205] [Ruby master Feature#12075] some	container#nonempty?

Issue #12075 has been updated by knu (Akinori MUSHA).


One of the selling points of `size?`, aside from the appearance of the name in the existing class File::Stat, is that it explicitly says it would check the size, which means it is essentially equivalent to `size > 0` and never like `each { true }` that can cause a side effect.  Plus, the Enumerator API has a `size` property (cf. `Enumerator.new(size) { ... }`) defined inside, so `Enumereator#size?` would really fit there.

----------------------------------------
Feature #12075: some container#nonempty?
https://bugs.ruby-lang.org/issues/12075#change-93611

* Author: naruse (Yui NARUSE)
* Status: Feedback
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
----------------------------------------
I sometimes write following code.

```ruby
ary = some_metho_returns_nil_or_empty_container() # nil or "" or [] or {}

if ary && !ary.empty?
  #  some code
end
```

But the condition `ary && !ary.empty?` is too long and complex.
Though Ruby 2.3 introduces `&.`, but this can���t be written as `ary&.empty?`.

One idea is add `nonempty?` write as `ary&.nonempty?`.

akr: `nonempty?` is not good name because human is not good at handling 

This discussion matches following core classes:

* String
* Array
* Hash



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>