Group: style
Maturity: experimental
Dart SDK: >= 2.10.0 • (Linter v0.1.118)
Since info is static, may be staleUse late
for private members with non-nullable types that are always expected
to be non-null. Thus it's clear that the field is not expected to be null
and it avoids null checks.
BAD:
int? _i;
m() {
_i!.abs();
}
GOOD:
late int _i;
m() {
_i.abs();
}
OK:
int? _i;
m() {
_i?.abs();
_i = null;
}
To enable the use_late_for_private_fields_and_variables
lint,
add use_late_for_private_fields_and_variables
under linter > rules in your
analysis_options.yaml
file:
linter:
rules:
- use_late_for_private_fields_and_variables