[#61171] Re: [ruby-changes:33145] normal:r45224 (trunk): gc.c: fix build for testing w/o RGenGC — SASADA Koichi <ko1@...>
(2014/03/01 16:15), normal wrote:
[#61243] [ruby-trunk - Feature #9425] [PATCH] st: use power-of-two sizes to avoid slow modulo ops — normalperson@...
Issue #9425 has been updated by Eric Wong.
[#61359] [ruby-trunk - Bug #9609] [Open] [PATCH] vm_eval.c: fix misplaced RB_GC_GUARDs — normalperson@...
Issue #9609 has been reported by Eric Wong.
(2014/03/07 19:09), normalperson@yhbt.net wrote:
SASADA Koichi <ko1@atdot.net> wrote:
[#61424] [REJECT?] xmalloc/xfree: reduce atomic ops w/ thread-locals — Eric Wong <normalperson@...>
I'm unsure about this. I _hate_ the extra branches this adds;
Hi Eric,
SASADA Koichi <ko1@atdot.net> wrote:
(2014/03/14 2:12), Eric Wong wrote:
SASADA Koichi <ko1@atdot.net> wrote:
[#61452] [ruby-trunk - Feature #9632] [Open] [PATCH 0/2] speedup IO#close with linked-list from ccan — normalperson@...
Issue #9632 has been reported by Eric Wong.
[#61496] [ruby-trunk - Feature #9638] [Open] [PATCH] limit IDs to 32-bits on 64-bit systems — normalperson@...
Issue #9638 has been reported by Eric Wong.
[#61568] hash function for global method cache — Eric Wong <normalperson@...>
I came upon this because I noticed existing st numtable worked poorly
(2014/03/18 8:03), Eric Wong wrote:
SASADA Koichi <ko1@atdot.net> wrote:
what's the profit from using binary tree in place of hash?
Юрий Соколов <funny.falcon@gmail.com> wrote:
[#61687] [ruby-trunk - Bug #9606] Ocassional SIGSEGV inTestException#test_machine_stackoverflow on OpenBSD — normalperson@...
Issue #9606 has been updated by Eric Wong.
[#61760] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — normalperson@...
Issue #9632 has been updated by Eric Wong.
[ruby-core:61476] [ruby-trunk - Bug #9573] descendants of a module don't gain its future ancestors, but descendants of a class, do
Issue #9573 has been updated by First Last. First Last wrote: > First Last wrote: > > First Last wrote: > > > Nobuyoshi Nakada wrote: > > > > > > > > `Class1` only knows `Mod1`, and its ancestor tree is copied into `Class2`. > > > > And ditto for including a module. > > > > > > I am inferring that the ancestor tree is copied into Class2 when it extends Class1, yes? > > > But at this time Mod1 has not yet been included, so how does Class2 learn of Mod1? > > > > > > and why is the situation different with modules? > > > > > > Do you see what I am pointing out, an ancestor added to a class, propagates to the **past** descendant of this class (Class2 extends Class1 **before** Mod1 is included in Class1), but an ancestor added to a module does not propagate to the **past** descendant of this module. > > > > Can someone please explain this phenomenon. What is the objection to explaining how this works? ---------------------------------------- Bug #9573: descendants of a module don't gain its future ancestors, but descendants of a class, do https://bugs.ruby-lang.org/issues/9573#change-45767 * Author: First Last * Status: Open * Priority: Normal * Assignee: * Category: * Target version: * ruby -v: ruby 2.1.1p76 (2014-02-24 revision 45161) [i686-linux] * Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- ```ruby module Mod1 end module Mod2 end class Class1 end class Class2 < Class1 end p Class2.ancestors - Object.ancestors # [Class2, Class1] Class1.include Mod1 p Class2.ancestors - Object.ancestors # [Class2, Class1, Mod1] Mod1.include Mod2 p Mod1.ancestors - Object.ancestors # [Mod1, Mod2] p Class2.ancestors - Object.ancestors # [Class2, Class1, Mod1] ``` ________________________________________________________________ note that descendants of a class do gain its future ancestors so 2 issues: 1. It would seem natural that in dynamic language, dynamically added ancestors should propagate to descendants 2. Why is there a difference in ancestor propagation between modules and classes -- http://bugs.ruby-lang.org/