ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Billy E Brand <bebrand52@gmail.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:72366] Re: [Ruby trunk - Feature #11747] \"bury\" feature, similar to 'dig' but opposite
Date: Fri, 18 Dec 2015 07:58:19 -0500	[thread overview]
Message-ID: <CA4EEE00-201C-44CE-9EC6-54DC2BB98EB2@gmail.com> (raw)
In-Reply-To: <71E32B49-E7CE-42FF-8409-EAF98B2028D0@gmail.com>

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

Remove me from mail list please 

Sent from my iPhone
Billy E Brand
404-597-9615

> On Dec 17, 2015, at 23:06, Joseph Jones <joeyi5216@gmail.com> wrote:
> 
> 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 this
>> data[:users][0][:name]
>> 
>> # we can do this w/o nil errors
>> data.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:
>> 
>> ~~~ruby
>> data.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: 3037 bytes --]

      reply	other threads:[~2015-12-18 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  4:06 [ruby-core:72269] [Ruby trunk - Feature #11747] \"bury\" feature, similar to 'dig' but opposite Joseph Jones
2015-12-18 12:58 ` Billy E Brand [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA4EEE00-201C-44CE-9EC6-54DC2BB98EB2@gmail.com \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).