Why Avoid Late Variables in Dart ??

?

Instance fields can be initialized in 4 ways:

1. At the point of protestation
2. In a constructor argument using 'this'
3. In the constructors initializer list before the law in braces starts.
4. Anywhere Differently

4 is problematic since the preface of null safety. By the time the constructor body( the law in braces) starts, the object must be completely initialized so each of its fields are usable. So if it isn't initialized in 1, 2, or 3, it fails to collect.
' ' .

It literally means I'll initialize it latterly . And you got no error.
.
.
.

:

- -

Still, you only know this at runtime when the program fails, If you forget to initialize a late variable. Basically, you say Trust me to initialize d ever before it's read for the first time . So the compiler skips the initialization check and inserts a runtime check.

-

-

-

There's a stir to allow skipping the initialization checks in some shapes. This may beget segfault which is harder to probe than an ordinary exception.

-

-

-

Your program needs to know if a late variable has been initialized or not. For this, the compiler frequently creates a retired internal variable that takes memory.

-

-

-

Every time you read a late variable the program must insure it's initialized, so a redundant check is added.

-

-

- .

Every time you write to a late variable the program sets the internal flag to note that it's initialized.

-

-

Hopefully, that helped. Did it?

Follow for further

Areeba Farooq