[go-nuts] Is this a compiler bug?

2017-01-06 Thread Konstantin Khomoutov
Isn't it that bit from [1] which deals with the arrays and structures of size 0? I mean that part which says distinct values of such types might have the same address in memory. 1. https://golang.org/ref/spec#Size_and_alignment_guarantees -- You received this message because you are subscribed

[go-nuts] Is this a compiler bug?

2017-01-06 Thread Konstantin Khomoutov
Isn't it that bit from [1] which deals with the arrays and structures of size 0? I mean that part which says distinct values of such types might have the same address in memory. 1. https://golang.org/ref/spec#Size_and_alignment_guarantees -- You received this message because you are subscribed

Re: [go-nuts] Is this a compiler bug?

2017-01-06 Thread Paul Jolly
Hopefully these points help to clarify things: - The types of the parameters to compare of the shout interface type - The comparison operator == therefore operates on two interface values. With reference to the spec ( https://golang.org/ref/spec#Comparison_operators): Interface values

[go-nuts] Is this a compiler bug?

2017-01-06 Thread Ignazio Di Napoli
I'm very curious about the answer to this unanswered StackOverflow question: http://stackoverflow.com/questions/41357948/what-golang-compiler-will-do-when-fmt-println import ( "fmt") type shout interface { echo()} type a struct {} func (*a) echo () { fmt.Println("a")} type b stru