[#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:79861] [Ruby trunk Bug#13257][Feedback] Symbol#respond_to?(:singleton_class) should be false (but true)
From:
matz@...
Date:
2017-03-02 09:27:08 UTC
List:
ruby-core #79861
Issue #13257 has been updated by Yukihiro Matsumoto. Status changed from Open to Feedback Fundamentally, `#respond_to?` is a method to check method existence. The class Symbol does have `#singleton_class` so that it's natural for it to return `true`, even though `#singleton_class` always fails. It seems you want to check the availability of functionality. That means you want to change the meaning of the method. I do not reject the proposal immediately, but at least it's controversial. Persuade us if you really want to change it. Matz. ---------------------------------------- Bug #13257: Symbol#respond_to?(:singleton_class) should be false (but true) https://bugs.ruby-lang.org/issues/13257#change-63292 * Author: Satoshi TAGOMORI * Status: Feedback * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin15] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- Objects of some classes doesn't have singleton classes (e.g., Symbol, Integer, Float...). Symbol#singleton_class raises TypeError. But Symbol#respond_to?(:singleton_class) returns true, and we cannot know when `#singleton_class` returns a valid class or raise errors in any way (except for calling it). Symbol#respond_to?(:singleton_class) should return false for such cases. (Integer, Float and other classes without singleton_class too.) -- 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>