Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Permalink for comment 552498
To read all comments associated with this story, please click here.
RE[17]: My thoughts on Go
by satsujinka on Thu 14th Feb 2013 20:58 UTC in reply to "RE[16]: My thoughts on Go"
Member since:

And what I keep saying is that "implements" doesn't do anything for readability.

The only thing "implements" does is force an object to have a certain signature. This is discussed in a different sub-thread in which the conclusion was:

Explicitly listing interfaces gives you compile time guarantees of what methods will exist, but if an object has the necessary signature for a different, non-listed interface then you don't get to use the object for that interface (even though the object would work.)

Implicitly implementing interfaces has the reverse features. You lose compile time guarantees of what methods are available, but you get to use the object anywhere it might make sense to.

Reply Parent Score: 2