
One thing I remember noticing that concerned me about Override on attributes is whether we'd force them in strict mode. An @override decorator does add some verbosity to code, but it lives on its own line and is syntactically quite separate from the important logic, I'm guessing there won't be strong objections to it (especially considering that most other popular object-oriented languages already require it). An `Override[...]` special form, on the other hand, will add quite a bit of inline verbosity to types, plus the interaction with type inference in `__init__` may be strange, if `__init__` doesn't call `super` (which is a good practice but not required by the runtime or as far as I know by most type checkers). So I could see people being less thrilled about a strict mode for attributes, I'm not sure how that would play out. It's certainly true that the same classes of bugs can be caught for attributes as for methods.