https://issues.dlang.org/show_bug.cgi?id=16318
Steven Schveighoffer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Steven Schveighoffer <[email protected]> --- Requiring override for implementing interface methods is too strict. If a class defines an interface, and doesn't implement a method, compilation fails. So we don't need that warning/error. Allowing override for interfaces is fine too. Often times, one decides that an abstract class really should be an interface or vice versa. To have to go through and update all the methods to say or not say override is useless busywork. Bottom line is that pure virtual functions should allow override, and not require it, no matter what the source. In effect, since implementing is REQUIRED, override keyword is a noop. --
