You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, --silent-imports prevents importing a module that defines the base class for some other class. The other class then implicitly inherits from Any, and this means that many operations on the instances of that class are not type-checked at all. I just fixed (#1365) an issue where something was type-checked without taking this unknown base class into account, and the result was an incorrect error. However there are also plenty of situations imaginable where this situation prevents useful type-checking from happening. So perhaps we should issue a warning in this situation (i.e. a base class being undefined due to an import being suppressed due to --silent-imports). Maybe --almost-silent could be augmented to also issue these warnings.
The text was updated successfully, but these errors were encountered:
Sometimes, --silent-imports prevents importing a module that defines the base class for some other class. The other class then implicitly inherits from Any, and this means that many operations on the instances of that class are not type-checked at all. I just fixed (#1365) an issue where something was type-checked without taking this unknown base class into account, and the result was an incorrect error. However there are also plenty of situations imaginable where this situation prevents useful type-checking from happening. So perhaps we should issue a warning in this situation (i.e. a base class being undefined due to an import being suppressed due to --silent-imports). Maybe --almost-silent could be augmented to also issue these warnings.
The text was updated successfully, but these errors were encountered: