From: Greg.mpls@... Date: 2017-03-25T15:26:46+00:00 Subject: [ruby-core:80323] [Ruby trunk Feature#13303] String#any? as !String#empty? Issue #13303 has been updated by MSP-Greg (Greg L). My vote for is for not needed, with second choice of `not_empty?`. 1) neg - I don't believe it's always necessary to have pairs of logical attributes/properties, as it certainly clutters up the namespace. 2) pos - Ruby already supports `if` / `unless` (we'll consider that not common) 3) pos - It makes for somewhat clearer code when a multi-criteria logical statement does not require the `!` operator. Conversely, all coders should immediately consider a `!` a not... So, I don't know if it's really needed... ---------------------------------------- Feature #13303: String#any? as !String#empty? https://bugs.ruby-lang.org/issues/13303#change-63798 * Author: naruse (Yui NARUSE) * Status: Feedback * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: ---------------------------------------- Once I proposed "some container#nonempty?" on #12075, and understand there's Array#any?. Today I found String doesn't have such method. -- https://bugs.ruby-lang.org/ Unsubscribe: