[ruby-core:72269] [Ruby trunk - Feature #11747] \"bury\" feature, similar to 'dig' but opposite

[Joseph Jones <joeyi5216@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

Joseph Jones liked your message with Boxer. On December 2, 2015 at 16:36:12 MST, dameyawn@gmail.com wrote:Issue #11747 has been updated by damien sutevski.Tsuyoshi Sawada wrote:> > inferred from the what the user is passing (such as a symbol or string for a hash or an integer for an array)> > I don't think this is a good idea. I think it should rather depend on the class of the receiver.> > {}.bury(:users, 0, :name, 'Matz') # => {:users => {0 => {:name => "Matz"}}}> [].bury(:users, 0, :name, 'Matz') # => error> {}.bury(0, 1, 2, :foo) # => {0 => {1 => {2 => :foo}}}> [].bury(0, 1, 2, :foo) # => [[nil, [nil, nil, :foo]]]> > and similar for struct.I agree. I should clarify that I was assuming the class of the receiver (`data`) was known in my example. The inference I was talking about was that a buried `0` would imply an array position by default instead of a hash key.----------------------------------------Feature #11747: "bury" feature, similar to 'dig' but opposite https://bugs.ruby-lang.org/issues/11747#change-55211* Author: damien sutevski* Status: Feedback* Priority: Normal* Assignee: Yukihiro Matsumoto----------------------------------------In Matz's recent Rubyconf talk, he used this example for the new 'dig' feature coming in Ruby 2.3:~~~ruby# we want thisdata[:users][0][:name]# we can do this w/o nil errorsdata.dig(:users, 0, :name)~~~What I'm proposing is a 'bury' feature that is the opposite of 'dig' in a sense. It inserts a value at an arbitrary depth, for example:~~~rubydata.bury(:users, 0, :name, 'Matz')~~~This will create a nested hash or an array automatically at each step if it doesn't already exist, and that can be inferred from the what the user is passing (such as a symbol or string for a hash or an integer for an array). It's similar to autovivification but more powerful!This behavior is very common, at least in my experience, so a dry method built into Ruby would be awesome! -- https://bugs.ruby-lang.org/     

[-- Attachment #2: Type: text/html, Size: 2535 bytes --]