Linter: deprecate `avoid_returning_null`
pq
All 3 comments
FWIW, it isn't clear to me that the rule has any value in a null safe world. If the return type is non-nullable, then returning null is a compiler error and a lint is useless. If the return type is nullable, then I'm proposing that we not produce a lint. Hence, I think the right course of action is to deprecate the lint and disable it in null safe code.
bwilkerson
on 11 May 2021
👍2
Agreed.
pq
on 11 May 2021
False positive
It states: "Avoid returning null from members whose return type is bool, double, int, or num"
but return type is not int but int?
consider improving this linter rule to distinct nullable types
subzero911
on 25 Jun 2021
Was this page helpful?
0 / 5 - 0 ratings
Related issues
jmagman
路
3Comments
devoncarew
路
5Comments
pasindud
路
4Comments
pq
路
4Comments
jelenalecic
路
3Comments
Most helpful comment
FWIW, it isn't clear to me that the rule has any value in a null safe world. If the return type is non-nullable, then returning null is a compiler error and a lint is useless. If the return type is nullable, then I'm proposing that we not produce a lint. Hence, I think the right course of action is to deprecate the lint and disable it in null safe code.