I realize that the issue might be about changing/ adding a builtin: - either add a builtin deep value Comparison function (via reflection) - or add a snapshot type refinement which triggers the allocation of an immutable copy of a reference type (and we would recover the behaviour of the string implementation which is a special case of []byte snapshot, i.e. a value type*)
I would still expect the behaviour previously mentioned for the "==" operator. (*) I keep using reference/value type terminology but it is indeed slightly tricky. But for lack of a better one... -- 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.
