From: "p8 (Petrik de Heus)" <noreply@...>
Date: 2021-08-19T06:57:04+00:00
Subject: [ruby-core:104992] [Ruby master Feature#12075] some	container#nonempty?

Issue #12075 has been updated by p8 (Petrik de Heus).


duerst (Martin D��rst) wrote in #note-28:

> I agree with @gotoken that `filled?` is confusing.

Yes, it might be confusing when you have an array like: `Array.new(3) # => [nil, nil, nil]`
Is it filled or not?

It's a bit longer, but `ary.populated?` doesn't have the capacity confusion.

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

* 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>