Change all late final Iterable fields to Lists #3649
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed a
late final Iterable<...>
field and thought to myself, "uh oh! That could be an expensive field!" The idea is that Iterables are lazy, so even if the field is "final", the Iterable calculations are re-executed on each access. So storing a lazily evaluated Iterable on a field seemed very scary 😱 . It may warrant a lint rule.Luckily, as I walked through the cases I found with grep, most of the values at runtime are Lists, not Iterables. Shwew. Still, I ran through and changed all of the signatures for future-proofing.
Two fields that were Iterables were converted to Lists. I did not benchmark.
Contribution guidelines:
dart format
.Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.