So that it becomes valid map inputs. What should be hashed would be the slice/map/ref type value.
On Wednesday, June 29, 2016 at 8:38:03 PM UTC+2, Konstantin Khomoutov wrote: > > On Wed, 29 Jun 2016 11:20:46 -0700 (PDT) > Chad <send...@gmail.com <javascript:>> wrote: > > > And actually the same for any other similar types such as maps... > > > > > > On Wednesday, June 29, 2016 at 8:19:45 PM UTC+2, Chad wrote: > > > > > > Just been thinking that since a slice is a "reference" type, why > > > not allow slice equality? > > > Of course the number of cases where two slices are equal would be > > > quite low, irrelevant of whether the view they have on their > > > respective arrays is the same. > > > > > > I'm thinking about something analogous to comparing pointer values. > > > No notion of deep equality as can be done via reflect. > > What would be the use cases? > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
