Feature #18950


Hash#slice fails to copy default block

Added by RubyBugs (A Nonymous) over 1 year ago. Updated over 1 year ago.

Target version:


An intense weekend debugging session discovered the following root cause of a bug: Hash#slice returns a new Hash, which has no default block set, even if the source Hash did have a default block set.

Simplified code to reproduce:

# Default to an empty hash for all accessed keys
hash_with_default = { |h, k| h[k] = {} } # => {}
hash_with_default[:a]                             # => {}
hash_with_default[:b]                             # => {}
hash_with_default                                 # => {:a=>{}, :b=>{}}

# Later, use Hash#slice
hash_sliced = hash_with_default.slice(:a, :b)     # => {:a=>{}, :b=>{}}

# Finally, access a new key
hash_sliced[:c]                                   # => nil

# Error -- that was expected to call the default block
raise "No default value" unless hash_sliced[:c] == {}

Updated by jeremyevans0 (Jeremy Evans) over 1 year ago

  • Tracker changed from Bug to Feature
  • ruby -v deleted (2.7.6)
  • Backport deleted (2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN)

Hash#slice documentation states it returns a new hash object, not a modified copy of the receiver. A new hash object by default does not have a default value or block. Hash#slice doesn't copy the default value either:[1] # => nil.

I don't think the current behavior is a bug, as there should be no expectation of the default value and block being copied. Hash#except, #select, #transform_keys, #transform_values, and maybe other methods that return new hashes and not modified copies do not copy over the default value or block.

That being said, this seems like a reasonable feature request.

Updated by Eregon (Benoit Daloze) over 1 year ago

This could lead to surprising behavior, e.g.:

cache = { |h,k| cache[k] = {} }
sliced = cache.slice(:a)
sliced[:foo] # => actually mutates cache with this proposal

Yes this would not be a problem if h[k] = {} is used as the block, but that's not always the case.

Also if we start copying the default value/block, it seems a slippery slope e.g. to copy instance variables, class, and other state too, which all seem not desirable (and even were decided against recently).

OTOH I guess copying compare_by_identity does make sense.


Also available in: Atom PDF