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
{{ message }}
Repository navigation
Remove "in checked mode" from documentation. #21066
From @jacob314 : "In the Flutter doc comments there are a lot of comments that start with "In checked mode" which should probably be updated to be consistent with Dart 2.
Dart 2 doesn't have a concept of checked vs unchecked mode. In Dart 1, unchecked mode meant ignore all type checks as well as ignore asserts.
In Dart2, --enable-asserts turns on asserts which is technically correct for these comments but a bit of a mouthful."
We should update any doc comments that reference "checked mode" with something appropriate.
I'd say that any reference to checked mode that is concerned with a user-written assert statement should refer to --enable-asserts, and all other references to checked mode should be removed, because the topic would then be checks added implicitly in checked mode with Dart 1, and those checks are always added to the program in Dart 2 (except maybe any such checks where we can prove at compile-time that they will always succeed, so it makes no difference to omit them), so we just stop talking about any particular mode, and keep the rest of the text unchanged.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
eernstg commentedon Aug 27, 2018
I'd say that any reference to checked mode that is concerned with a user-written
assertstatement should refer to--enable-asserts, and all other references to checked mode should be removed, because the topic would then be checks added implicitly in checked mode with Dart 1, and those checks are always added to the program in Dart 2 (except maybe any such checks where we can prove at compile-time that they will always succeed, so it makes no difference to omit them), so we just stop talking about any particular mode, and keep the rest of the text unchanged.Sfshaza commentedon Aug 28, 2018
In case someone wants to review (@gspencergoog, @eernstg), here's the short PR: flutter/website#1191
Checked mode wasn't used much on flutter.io. It may be used more on docs.flutter.io.
eernstg commentedon Aug 28, 2018
I just added a single comment about the description of
assertstatements.zoechi commentedon Dec 7, 2018
I still found a few
https://www.google.at/search?q=site%3Aflutter.io+%22checked+mode%22&oq=site%3Aflutter.io+%22checked+mode%22&aqs=chrome..69i57j69i58.7153j0j7&sourceid=chrome&ie=UTF-8
...
Remove checked mode references (#146845)
Remove checked mode references (flutter#146845)
github-actions commentedon Apr 30, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.