From: jasondenney@... Date: 2016-04-12T01:44:51+00:00 Subject: [ruby-core:74883] [Ruby trunk Bug#12269] Nesting Two-levels of Hash with Hash as default value makes top level Hash not list keys/values and causes reference issue with nested values. Issue #12269 has been reported by Jason Denney. ---------------------------------------- Bug #12269: Nesting Two-levels of Hash with Hash as default value makes top level Hash not list keys/values and causes reference issue with nested values. https://bugs.ruby-lang.org/issues/12269 * Author: Jason Denney * Status: Open * Priority: Normal * Assignee: * ruby -v: 2.3.0 * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- Nesting Hashes that have Hashes as default values cause the 1st (top) level hash to not list keys or values. Also, it is possible to overwrite the values of keys in the 2nd level hash via new assignments to entirely different keys on the 2nd level hash. See the following IRB session for behavior: ~~~ 2.3.0 :001 > h = Hash.new( Hash.new({}) ) => {} 2.3.0 :002 > h['a']['b']['c'] = true => true 2.3.0 :003 > h.inspect => "{}" 2.3.0 :004 > h['a']['b']['c'] => true 2.3.0 :005 > h['a']['Z']['c'] = false => false 2.3.0 :006 > h['a']['b']['c'] => false ~~~ The only vaguely related bug report I could find was: [[https://bugs.ruby-lang.org/issues/12098]] -- https://bugs.ruby-lang.org/ Unsubscribe: