As the title says. There is no point in having this in interfaces / regulars.
- Differential Revisions
- D7673: eolian: ensure regular class cannot have a pure_virtual property/method
- D7671 / rEFLba065f9eed25: evas: make classes abstract
D7670 / rEFL0a95767a0c95: efl_net: make efl.net.server.fd abstract
D7669 / rEFL48b43928bbbe: ecore_audio: remove pure virtual functions from classes
- Mentioned Here
- rEFL18ab4f2eec44: eolian: disallow pure virtual on non-abstract/mixin classes
rEFL90f604327586: eolian: disallow @pure_virtual keyword in interfaces
rEFL211064113104: eolian: add validation to make sure all methods are implemented
rEFLeb830d8e46ce: eolian: disallow pure virtual methods in regular classes
I added a check to help with this in eb830d8e46ce5aae656bc7d93a4d01bac0a82e5d. Methods/properties are implicitly pure_virtual in interfaces, so the ticket is a bit misleading, and it's currently also allowed (and used) in mixins. However, pure virtual methods are treated as unimplemented by 211064113104702b2c6bd279e9e8a04ee0e8254a, so any potential cases are caught by that.