avoid_init_to_null issue doesn't show when declared const

[Acid-Free]

What happened?

When assigning null to a newly declared variable, avoid_init_to_null issue shows up in the bottom-right of the screen.

However, when declared as const, the issue disappears.

Steps to reproduce problem

1. Define a constant variable [with const]

Additional info

Browser

Browser: firefox

Version: 107.0 (64-bit)

Are you using any extensions/plugins that affect website behavior
(particularly those that affect iframes, such as ad blockers)?

Are there any warnings or errors in your browser's JavaScript console?
If so, paste them below:

[paste warnings or errors here]

Machine

Operating system: Windows 10 Home Single Language

Version: 19044.2251

Code

main() {
  const int? a = null;
  print(a);
}

[parlough]

Thanks for filing an issue!

This is expected because const declarations must be initialized in the declaration and cannot change, so if you want it to be null, you need to explicitly do so.

Note the lint also won't appear if the declaration is final as final variables cannot be read/accessed until assigned, so if you want it to be null and use that variable, you need to explicitly do so.

void main() {
  final int? a = null;
  print(a);
}

The lint is intended for variable declarations (using var or just a simple type declaration such as int?) with a nullable type as they automatically get initialized to null.

I've noticed the current description of the lint hasn't been updated for null safety, so I've gone ahead and done that in dart-archive/linter#3863. Thanks again for opening an issue!