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
In general, we want to let user limit Any types used in their code.
What we have currently is a --warn-return-any flag. Moreover, there are two open PRs:
Both of these PRs need better names for their flags. I was thinking something like --disable-any-from-unanalyzed-module and --warn-incomplete-generic-type.
I think we should try to provide as much control as possible and have both of these flags in. And then have some more general flag to enable both of them. @JukkaL suggested that perhaps we could use --strict for it.
Alternatively, we can have two flags (something like the following: --disallow-implicit-any and --disallow-all-any).
The text was updated successfully, but these errors were encountered:
In general, we want to let user limit Any types used in their code.
What we have currently is a
--warn-return-any
flag. Moreover, there are two open PRs:Both of these PRs need better names for their flags. I was thinking something like
--disable-any-from-unanalyzed-module
and--warn-incomplete-generic-type
.I think we should try to provide as much control as possible and have both of these flags in. And then have some more general flag to enable both of them. @JukkaL suggested that perhaps we could use
--strict
for it.Alternatively, we can have two flags (something like the following:
--disallow-implicit-any
and--disallow-all-any
).The text was updated successfully, but these errors were encountered: