override and interface methods

[Andrea Fontana]

On Monday, 29 October 2018 at 14:47:35 UTC, FeepingCreature wrote:
> I agree that it's not overriding anything, but it also makes 
> little sense to add a new keyword "implement" that is used as a 
> 1:1 stand-in for override for interface methods, and in any 
> case what would you do in the class/interface case: "override 
> implement void foo()"? And besides, override is *already* 
> permissible for interface implementations, so it already means 
> "override or implement". I'm just asking for some consistency.

Wait, no.

You can simply avoid using override at all for interface. And add 
it only if you're overriding a class method.

Andrea