When a @protected method (such as State.dispose) is overridden, it loses its "protected" status unless the annotation is re-applied.

This has resulted in some less-than-ideal Flutter autofill suggestions:

Proposal

Maybe the @reopen annotation's usage could be expanded to cover class fields as well: restrictive annotations like @protected would apply to any subtype's overridden fields by default, unless the field is "re-opened".

(Would an analyzer change like this one count as "breaking"?)