From: Joseph Jones <joeyi5216@...>
Date: 2015-12-17T21:06:25-07:00
Subject: [ruby-core:72269]  [Ruby trunk - Feature #11747] \"bury\" feature, similar to 'dig' but opposite

--56738641_4516dde9_16c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Joseph Jones liked your message with Boxer. On December 2, 2015 at 16:36:=
12 MST, dameyawn=40gmail.com wrote:Issue =2311747 has been updated by dam=
ien 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 arra=
y)> > I don't think this is a good idea. I think it should rather depend =
on the class of the receiver.> > =7B=7D.bury(:users, 0, :name, 'Matz') =23=
 =3D> =7B:users =3D> =7B0 =3D> =7B:name =3D> =22Matz=22=7D=7D=7D> =5B=5D.=
bury(:users, 0, :name, 'Matz') =23 =3D> error> =7B=7D.bury(0, 1, 2, :foo)=
 =23 =3D> =7B0 =3D> =7B1 =3D> =7B2 =3D> :foo=7D=7D=7D> =5B=5D.bury(0, 1, =
2, :foo) =23 =3D> =5B=5Bnil, =5Bnil, nil, :foo=5D=5D=5D> > and similar fo=
r struct.I agree. I should clarify that I was assuming the class of the r=
eceiver (=60data=60) was known in my example. The inference I was talking=
 about was that a buried =600=60 would imply an array position by default=
 instead of a hash key.----------------------------------------=46eature =
=2311747: =22bury=22 feature, similar to 'dig' but opposite https://bugs.=
ruby-lang.org/issues/11747=23change-55211* Author: damien sutevski* Statu=
s: =46eedback* 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:=7E=7E=7Eruby=23 we =
want thisdata=5B:users=5D=5B0=5D=5B:name=5D=23 we can do this w/o nil err=
orsdata.dig(:users, 0, :name)=7E=7E=7EWhat I'm proposing is a 'bury' feat=
ure that is the opposite of 'dig' in a sense. It inserts a value at an ar=
bitrary depth, for example:=7E=7E=7Erubydata.bury(:users, 0, :name, 'Matz=
')=7E=7E=7EThis will create a nested hash or an array automatically at ea=
ch step if it doesn't already exist, and that can be inferred from the wh=
at the user is passing (such as a symbol or string for a hash or an integ=
er for an array). It's similar to autovivification but more powerful=21Th=
is behavior is very common, at least in my experience, so a dry method bu=
ilt into Ruby would be awesome=21 -- https://bugs.ruby-lang.org/     
--56738641_4516dde9_16c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><body><div>Joseph Jones liked your message with <a href=3D=22http:/=
/bxr.io/PBIqo=22>Boxer</a>.</div><br/><br/><div><div class=3D=22quote=22>=
On December 2, 2015 at 16:36:12 MST, dameyawn=40gmail.com wrote:<br/><blo=
ckquote type=3D=22cite=22 style=3D=22border-left-style:solid;border-width=
:1px;margin-left:0px;padding-left:10px;=22>Issue =2311747 has been update=
d by damien sutevski.<br /><br /><br />Tsuyoshi Sawada wrote:<br />> >  i=
nferred from the what the user is passing (such as a symbol or string for=
 a hash or an integer for an array)<br />> <br />> I don't think this is =
a good idea. I think it should rather depend on the class of the receiver=
.<br />> <br />>     =7B=7D.bury(:users, 0, :name, 'Matz') =23 =3D> =7B:u=
sers =3D> =7B0 =3D> =7B:name =3D> =22Matz=22=7D=7D=7D<br />>     =5B=5D.b=
ury(:users, 0, :name, 'Matz') =23 =3D> error<br />>     =7B=7D.bury(0, 1,=
 2, :foo) =23 =3D> =7B0 =3D> =7B1 =3D> =7B2 =3D> :foo=7D=7D=7D<br />>    =
 =5B=5D.bury(0, 1, 2, :foo) =23 =3D> =5B=5Bnil, =5Bnil, nil, :foo=5D=5D=5D=
<br />> <br />> and similar for struct.<br /><br />I agree. I should clar=
ify that I was assuming the class of the receiver (=60data=60) was known =
in my example. The inference I was talking about was that a buried =600=60=
  would imply an array position by default instead of a hash key.<br /><b=
r /><br /><br /><br />----------------------------------------<br />=46ea=
ture =2311747: =22bury=22 feature, similar to 'dig' but opposite <br />ht=
tps://bugs.ruby-lang.org/issues/11747=23change-55211<br /><br />* Author:=
 damien sutevski<br />* Status: =46eedback<br />* Priority: Normal<br />*=
 Assignee: Yukihiro Matsumoto<br />--------------------------------------=
--<br />In Matz's recent Rubyconf talk, he used this example for the new =
'dig' feature coming in Ruby 2.3:<br /><br />=7E=7E=7Eruby<br />=23 we wa=
nt this<br />data=5B:users=5D=5B0=5D=5B:name=5D<br /><br />=23 we can do =
this w/o nil errors<br />data.dig(:users, 0, :name)<br />=7E=7E=7E<br /><=
br />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:<br />=
<br />=7E=7E=7Eruby<br />data.bury(:users, 0, :name, 'Matz')<br />=7E=7E=7E=
<br /><br />This will create a nested hash or an array automatically at e=
ach step if it doesn't already exist, and that can be inferred from the w=
hat the user is passing (such as a symbol or string for a hash or an inte=
ger for an array). It's similar to autovivification but more powerful=21<=
br /><br />This behavior is very common, at least in my experience, so a =
dry method built into Ruby would be awesome=21 <br /><br /><br /><br />--=
 <br />https://bugs.ruby-lang.org/<br /></blockquote></div></div></body><=
/html>
--56738641_4516dde9_16c--