Thank you very much for your response! I definitely understand what you are getting at, but I don't think that it's technically correct. For instance,
https://golang.org/ref/spec#Interface_types seems to pretty clearly say that an interface is a type. Moreover, there is the possibility of "typing" a variable as an interface that has neither a dynamic type nor dynamic value: var i interface{} has the type interface{} and it's dynamic type and value are both nil. That said, again, I agree with the sentiment of your statement and it is exactly the point that I was hoping to clarify with this conversation. Thanks again for your response! Will On Tuesday, June 20, 2017 at 1:50:16 AM UTC-4, Tamás Gulácsi wrote: > > AFAIK an interface is not a type, just behavior, and a type may implement > an interface, so each variable will have a concrete type. > An variable with interface "type" will have a named interface and a > specific type which implements it. -- 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.
