Aaron Patterson wrote: > We should probably get Aman's opinion on this since he wrote the initial heap dumping code. Personally, I would like to see this feature enabled with a flag. It seems like it will significantly increase the si...yosiat (Yosi Attias)
Yosi Attias wrote: > Nobuyoshi Nakada wrote: > ... Hi, I have added to reflect the new logic: * If the key/value are special consts - I write the "to_s" value of them (:a => "a", 1 => "1") * If the key/value are not special consts -...yosiat (Yosi Attias)
Nobuyoshi Nakada wrote: > That distinction makes no sense. > ... Oh.. I understand what you are saying, I will fix that! Just to make sure I understand your position, you say this distinction is not needed, and in case of this hash: ...yosiat (Yosi Attias)
Nobuyoshi Nakada wrote: > Yosi Attias wrote: > ... Yes, but how can you distinguish between string value which is address or address to other ruby object: `h = {a: "0x007f8f3c8baf88"}` to `h = {a: {b: 1}}` yosiat (Yosi Attias)
Nobuyoshi Nakada wrote: > Are `is_{key,value}_address` necessary? Yes, If the key/value are composite objects (not special consts, like string/hash/class) then the values of "key"/"value" should be address which is *pointer to other ...yosiat (Yosi Attias)
Hi, *This is my first c code contribution :)* I am helping developing heap-analyzer (github.com/tenderlove/heap-analyzer), and currently the dumps lacks of "type metadata" information, like: * Hash entries - the keys and value ...yosiat (Yosi Attias)
yosiat (Yosi Attias)09:37 PM Ruby Feature #11599: Dump entries of hash in ObjectSpace