[#79914] [Ruby trunk Bug#13282] opt_str_freeze does not always dedupe — normalperson@...
Issue #13282 has been reported by Eric Wong.
4 messages
2017/03/05
[#80140] [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus) — shyouhei@...
Issue #13295 has been updated by shyouhei (Shyouhei Urabe).
5 messages
2017/03/13
[#80362] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— Eric Wong <normalperson@...>
2017/03/26
shyouhei@ruby-lang.org wrote:
[#80368] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— SASADA Koichi <ko1@...>
2017/03/27
On 2017/03/26 15:16, Eric Wong wrote:
[#80205] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint — Eric Wong <normalperson@...>
duerst@ruby-lang.org wrote:
4 messages
2017/03/17
[#80213] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint
— Martin J. Dürst <duerst@...>
2017/03/17
Hello Eric,
[#80290] [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch — normalperson@...
Issue #13355 has been reported by normalperson (Eric Wong).
4 messages
2017/03/23
[#80410] Re: [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch
— Eric Wong <normalperson@...>
2017/03/27
normalperson@yhbt.net wrote:
[#80415] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
5 messages
2017/03/28
[#80488] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
4 messages
2017/03/29
[ruby-core:80295] [Ruby trunk Feature#13303] String#any? as !String#empty?
From:
shevegen@...
Date:
2017-03-23 20:32:41 UTC
List:
ruby-core #80295
Issue #13303 has been updated by shevegen (Robert A. Heiler). Actually the name .nonempty? is easier to understand than .any? in this context, or non-empty strings. I think the only problem is that "nonempty" reads very ... strangely. I can not come up with a good name either though. .non_empty? May seem obvious but I am not sure either there since it is quite long. I think that nonempty? or non_empty? is better than any? in this context though. Ignoring the ruby parser, I guess this here would be one of the shortest, somewhat natural way to query and ask on an object: object, are you not empty object not empty? I guess the most natural ruby way would still be object.not_empty? object.non_empty? Or perhaps we can ask any container/object if it has at least one entry. :\ object.at_the_least_one_entry? The last one is a bit awful though - now .non_empty? or .non_empty? or .not_empty? would look nicer. :))) ---------------------------------------- Feature #13303: String#any? as !String#empty? https://bugs.ruby-lang.org/issues/13303#change-63765 * 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>