-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update old examples involving implicit downcasts #3304
Comments
@bwilkerson Does analyzer:
strong-mode:
implicit-casts: false Sidenote: If it doesn't have any functionality anymore, perhaps there could be a hint/lint with an explanation why it's not useful anymore. |
I think that's been replaced by other flags, but @srawlins would know more definitively. But yes, I agree that if it's deprecated / dead then we should remove it from the external docs and have a warning for it. |
|
If you're using 2.12/2.13 but your lower SDK bound is before that (i.e. you haven't opted into null safety), does (I'm wondering whether we need to have wording that reflects language version rather than SDK version.) |
That's correct, it would. |
Update examples in analyzer documentation and type system documentation around implicit downcasts since they were removed with null safety. There may be other cases as well.
The example in Enabling stricter type checks is no longer relevant as it won't work without the option anyway.
As we migrate The Dart type system article we'll need to keep this in mind as well.
The text was updated successfully, but these errors were encountered: