[#83096] File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?}) — Nobuyoshi Nakada <nobu@...>
On 2017/10/04 8:47, [email protected] wrote:
5 messages
2017/10/04
[#83100] Re: File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?})
— Eric Wong <normalperson@...>
2017/10/04
Nobuyoshi Nakada <[email protected]> wrote:
[#83105] Re: File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?})
— Nobuyoshi Nakada <nobu@...>
2017/10/04
On 2017/10/04 15:55, Eric Wong wrote:
[#83107] Alias Enumerable#include? to Enumerable#includes? — Alberto Almagro <albertoalmagro@...>
Hello,
9 messages
2017/10/04
[#83113] Re: Alias Enumerable#include? to Enumerable#includes?
— "Urabe, Shyouhei" <shyouhei@...>
2017/10/05
This has been requested countless times, then rejected each and every time.
[#83129] Re: Alias Enumerable#include? to Enumerable#includes?
— Alberto Almagro <albertoalmagro@...>
2017/10/05
Sorry I didn't found it on the core mail list's archive.
[#83138] Re: Alias Enumerable#include? to Enumerable#includes?
— "Urabe, Shyouhei" <shyouhei@...>
2017/10/06
Ruby has not been made of popular votes so far. You have to show us
[#83149] Re: Alias Enumerable#include? to Enumerable#includes?
— Eric Wong <normalperson@...>
2017/10/06
Alberto Almagro <[email protected]> wrote:
[#83200] [Ruby trunk Feature#13996] [PATCH] file.c: apply2files releases GVL — normalperson@...
Issue #13996 has been reported by normalperson (Eric Wong).
4 messages
2017/10/10
[ruby-core:83114] [Ruby trunk Bug#13973] super_method fails on some UnboundMethods
From:
ruby-core@...
Date:
2017-10-05 02:01:35 UTC
List:
ruby-core #83114
Issue #13973 has been reported by marcandre (Marc-Andre Lafortune). ---------------------------------------- Bug #13973: super_method fails on some UnboundMethods https://bugs.ruby-lang.org/issues/13973 * Author: marcandre (Marc-Andre Lafortune) * Status: Open * Priority: Normal * Assignee: nobu (Nobuyoshi Nakada) * Target version: 2.5 * ruby -v: trunk * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- `super_method` fails to go up the ancestry chain for methods that are only defined in included modules: ~~~ ruby module A def foo end end module B def foo end end class C include A include B end class D def foo end include A include B end C.instance_method(:foo) # => #<UnboundMethod: C(B)#foo> (ok) C.instance_method(:foo).super_method # => nil (wrong, should be <UnboundMethod: <something>(A)#foo>) C.new.method(:foo).super_method # => #<Method: Object(A)#foo> (ok) D.instance_method(:foo).super_method # => #<UnboundMethod: Object(B)#foo> (ok) D.instance_method(:foo).super_method.super_method # => #<UnboundMethod: Object(A)#foo> (ok) ~~~ Note that the results for C and D's super_method differ slightly, with one outputing "C(B)" and the other "Object(B)". I don't understand why "Object" shows anywhere in my example. I would have expected the output to be "D(B)" in the later case. Should I open a different issue for this? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>