Which is why it should be formalized. Where is the inconsistency between slices and arrays? Why do people even think that a slice need to behave like an array wrt equality, were it introduced?
A slice is not an array! On Sunday, July 3, 2016 at 11:36:44 AM UTC+2, as....@gmail.com wrote: > > Relaxing unformalized behavior makes little sense to me. Explaining why > equality is inconsistent between slices and arrays is not something I want > to do either. > > > On Sunday, July 3, 2016 at 1:40:19 AM UTC-7, Chad wrote: >> >> Rob and Robert actually wrote that this area of the spec needs more >> work... >> Otherwise, the behaviour of maps, slices and funcs cannot be fully >> explained. >> >> On Sunday, July 3, 2016 at 7:25:31 AM UTC+2, as....@gmail.com wrote: >>> >>> Go does not have reference types. As far as I know, the word was >>> purposefully removed from the spec to remove the ambiguity surrounding the >>> word. >>> >>> https://groups.google.com/forum/m/#!topic/golang-dev/926npffb6lA >> >> >> >> @Martin >> >> As I've mentioned earlier, one ought to be careful about false friends >> from other languages. >> I am not sure I understand what you mean by: >> >> if the name field is changed after the call >> >> >> -- 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.
