The semantics of + and append() preclude a "data aliasing" ambiguity.
c = a + b
c = append(a, b...)
On Friday, September 16, 2016 at 9:14:45 PM UTC+1, Thomas Bushnell, BSG
> The values of the summation are indeed unambiguous, but the data aliasing
> properties are not.
>> Thank you both.
>> To Ian: but a slice is not a matrix or a list.
>> To Axel: append() and copy() compliment indexing and slicing well enough.
>> It would be a shame if ambiguity is indeed the reason. We've accepted 1 +
>> 1 as numeric addition and "a" + "b" as string concatenation. For a slice,
>> perceived as a window on a string of elements, concatenation is
>> unambiguous. [a, b, c] + [x, y, z] = [a, b, y, z]
>> On Friday, September 16, 2016 at 6:11:17 PM UTC+1, oyi...@gmail.com
>>> I have not been able to find an explanation. Does anyone care to explain
>>> or point to relevant documentation?
>> 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
>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.