On Monday, July 4, 2016 at 12:09:57 AM UTC+2, as....@gmail.com wrote:
>
> I wish I could be pointed to such discussion.
>>
>
> It was briefly discussed in *The Go Programming Language *book by Donovan 
> & Kernighan (p 132)
>
> *:*
>
>> An analogous “shallow” equality test for slices could be useful, and it 
>> would solve the problem with maps, but the inconsistent treatment of slices 
>> and arrays by the == operator would be confusing. The safest choice is to 
>> disallow slice comparisons altogether. 
>
>
A claim I find safe to be in disagreement with.
 

>
> Given this program, how would you modify it to include interfaces?
>
> https://play.golang.org/p/9-rhDCZol_
>

Starbytes is a pointer to a slice. It does not make a lot of sense to begin 
with.
I am pointing out the fact that if you have interfaces holding a slice, the 
current behaviour is not specified. (as in the Go's spec). That's a bug.

-- 
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.

Reply via email to