From: Fuad Saud Date: 2013-08-18T22:10:15-03:00 Subject: [ruby-core:56738] Re: [ruby-trunk - Feature #7739] Define Hash#| as Hash#reverse_merge in Rails --001a11c28c4c62147904e4429af0 Content-Type: text/plain; charset=ISO-8859-1 Sorry, I swapped | for + in the last message. On Aug 18, 2013 5:01 PM, "David MacMahon" wrote: > > On Aug 18, 2013, at 12:34 PM, fuadksd (Fuad Saud) wrote: > > > Matz rejected (({+})) for merging, as it is different than addition. > > My understanding was that Matz rejected #+ for merging because of a > concern about how to resolve key conflicts. Maybe his concern can be > addressed by providing two Hash operators (e.g. #| for reverse_merge-like > behavior and #+ for merge-like behavior) each with distinct and well > defined resolutions for conflicting keys. > > Dave > > --001a11c28c4c62147904e4429af0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Sorry, I swapped | for + in the last message.

On Aug 18, 2013 5:01 PM, "David MacMahon&qu= ot; <davidm@astro.berkeley.= edu> wrote:

On Aug 18, 2013, at 12:34 PM, fuadksd (Fuad Saud) wrote:

> Matz rejected (({+})) for merging, as it is different than addition.
My understanding was that Matz rejected #+ for merging because of a concern= about how to resolve key conflicts. =A0Maybe his concern can be addressed = by providing two Hash operators (e.g. #| for reverse_merge-like behavior an= d #+ for merge-like behavior) each with distinct and well defined resolutio= ns for conflicting keys.

Dave

--001a11c28c4c62147904e4429af0--