From: her@... Date: 2016-09-26T18:27:17+00:00 Subject: [ruby-core:77412] [Ruby trunk Feature#12075] some container#nonempty? Issue #12075 has been updated by sorah Shota Fukumori. I know any? works on some use cases, but I'm positive to have a proposed method because using `any?` has a pitfall. We have to guarantee an array doesn't have only false or nil. Also I'm worrying users who started to use `any?` for this use case, but doesn't know this pitfall. I'm positive on Object#not idea. ---------------------------------------- Feature #12075: some container#nonempty? https://bugs.ruby-lang.org/issues/12075#change-60668 * Author: Yui NARUSE * Status: Feedback * Priority: Normal * Assignee: 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: