[meta] Make Dart repos sound null safe

[devoncarew]

This is a meta issue used to track the progress on making various Dart repos sound null safe. This must happen prior to null safety becoming the only supported mode.

Published packages

• Package dart_syntax_highlight needs to be migrated to null safety dart-syntax-highlight#25
• Package dump_viz needs to be migrated to null safety dart-archive/dump-info-visualizer#37
• Found 3 files excluded from sound null safety in build_runner/ build#3315
• Found 1 file excluded from sound null safety in build_test/ build#3316
• Found 1 file excluded from sound null safety labs#82
• Found 1 file excluded from sound null safety language#2274
• Found 23 files excluded from sound null safety #58754
• Found 9 files excluded from sound null safety in pkg/analyzer/ #49176
• Found 1 file excluded from sound null safety in pkg/dds/ #49177
• Found 2 files excluded from sound null safety in pkgs/shelf/ shelf#238
• Found 2 files excluded from sound null safety source_gen#605
• Found 1 file excluded from sound null safety tools#1782
• Found 4 files excluded from sound null safety in pkgs/test/ test#1707
• Migrate dwds to null safety webdev#1327
• Found 3 files excluded from sound null safety in frontend_server_client/ webdev#1637
• Found 1 file excluded from sound null safety google/built_collection.dart#261
• Found 1 file excluded from sound null safety google/mono_repo.dart#393
• Found 1 file excluded from sound null safety google/protobuf.dart#672
• Found 1 file excluded from sound null safety in pkg/vm_service/ #49184
• Package intl_translation needs to be migrated to null safety i18n#593
• Found 34 files excluded from sound null safety in webdev/ webdev#1640

Non-published SDK packages

• pkg/test_runner (an infra package) has not yet migrated to null safety #49213
• pkg/dart2js_info needs to be migrated to null safety #49214
• [ddc] Migrate pkg/dev_compiler to null safety #46617
• pkg/frontend_server has 10 files opted out of null safety #49212
• Migrate pkg/compiler to null safety #50008

Info

Packages listed here should either be converted to null safety (indicated by having a lower SDK bounds of 2.12), and make sure that no files are excluded from null safety (no files have a language comment of // @dart=2.7, // @dart=2.8, // @dart=2.9, // @dart=2.10, or // @dart=2.11).

Note that we're only trying to find unintentional file opt-outs above - null safety conversions that weren't quite finished.

If the opt-out is intentional - there in order to test the opt-out handling and / or pre-null safe behavior - please update / edit / close the issue as appropriate. Additionally, consider adding a token on the line before the opt-out - // null_safety_optout_testing. This will allow tools to ignore the opt-out when looking for unmigrated files, and, allow us to find and remove all null safe testing opt-outs at a later date. For cases like these, the full opt-out may then look something like:

// null_safety_optout_testing
// @dart=2.10

[natebosch]

Some of these are intentional. We run tests which are not null safe in some packages to validate some specific unsound mode behavior. A bunch are in files that are named with a suffix of _opt_out_test.dart.
Should we try to find a convention for this and exclude it from the search?

[devoncarew]

This was likely a one-shot search. If we need to update the grep logic to be more accurate, we certainly can. But it may be enough to just update the individual issues - reduce the hits found or close the issue entirely.

[mit-mit]

All done 🥳