This would probably introduce unnecessary confusion. People are used to the equality operator comparing values in go, as opposed to references. It's much better if the slices finally support the equality operator, even though the comparison speed will depend on the number of items in the slices.
On Wednesday, June 29, 2016 at 9:19:45 PM UTC+3, 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. > > > > > -- 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.
