Hi all,

 

It's almost awkward to bother the list with this humble RFC amidst so many
exciting proposals :)

 

With help from Ilija and Niels the implementation is now working and tested,
so the RFC seems getting closer to the voting phase.

 

Ilija raised a point about optional interfaces not being a reliable
"overridable" for `#[Override]`. I can certainly understand that concern.

 

At the same time I think there could be value in being able to say "although
all overridables are optional, this method must override something, so at
least one of them must be present". This would be applicable when a package
provides compatibility with multiple tools (or versions of a tool), but
still requires at least one of them to be present. Besides I think that
using `#[Override]` with an optional interface would be a very deliberate
step so such consequences would be not only expected, but intended.

 

I've added an example illustrating this to the RFC. Does this justification
make sense or does it sound like a horrible design? Would it be better
suited for a secondary vote? I haven't yet investigated how complex it would
be to let Overrides ignore optional interfaces as non-existant.

 

Does anyone have strong feelings on this or any other concerns?

 

BR,

Juris

Reply via email to