PEP 698: Change the wording for strict mode section (#2874)
At this time, Pyre still does not have strict override enforcement. This (and supporting codemod tools) are still something we want, but given that we have not yet delivered this and do not have a firm ETA we should not make claims about specific plans in the PEP text.
This commit is contained in:
parent
38192e0ba9
commit
848d0908c9
|
@ -228,8 +228,10 @@ principle.
|
|||
Strict Enforcement Per-Project
|
||||
==============================
|
||||
|
||||
We plan to make the use of ``@override`` required in Pyre’s strict mode. This
|
||||
is a feature we believe most type checkers would benefit from.
|
||||
We believe that ``@override`` is most useful if checkers also allow developers
|
||||
to opt into a strict mode where methods that override a parent class are
|
||||
required to use the decorator. Strict enforcement should be opt-in for backward
|
||||
compatibility.
|
||||
|
||||
|
||||
Motivation
|
||||
|
|
Loading…
Reference in New Issue