News for hackers. Stuff that matters.
Re:Interfaces Generally Belong with Users by kubanczyk on Saturday November 23, 2019 @04:26PM (#21616678)
Not like "extends" or "implements".

If a class implements all the methods of the interface (as seen at compile-time - same method name, arguments, returns) then that's it, period. Compiler will allow you to use it. Beyond that the interface doesn't "know" about the class and the class doesn't "know" about the interface.

So it doesn't matter the interface didn't even exist when that class was written.

Re:Interfaces Generally Belong with Users by hesk on Saturday November 23, 2019 @04:29PM (#21616694)
Sounds a lot like Python's duck typing to me. (Although Python would coerce the types if they don't match.)
Re:Interfaces Generally Belong with Users by kevincox on Saturday November 23, 2019 @04:54PM (#21616853)
It is. "Structural typing" is basically "compile time duck typing".

One major notable advantage is that you are checking the existence of every method you may call, not just the ones your tests happen to use.

Re:Interfaces Generally Belong with Users by Too on Sunday November 24, 2019 @03:39AM (#21619165)
Javascript (without typescript) also has duck typing. The difference with structural typing is that the interface is formalized and enforced compile time.

Python 3.7 added compile structural typing using what they call Protocols. It works very similar to typescript. See https://www.python.org/dev/peps/pep-0544/

Re:Interfaces Generally Belong with Users by mcqueenjordan on Saturday November 23, 2019 @05:53PM (#21617162)
Similar in some ways, but duck typing is a misnomer because it doesn't involve typing.

These are type classes, or what Rust calls Traits.

Re:Interfaces Generally Belong with Users by aboodman on Saturday November 23, 2019 @07:56PM (#21617642)
> duck typing is a misnomer because it doesn't involve ...

dang, the joke was so close