void_checks: allow assigning any future to a FutureOr<void> #4699
Labels
P3
A lower priority bug or feature request
set-core
Affects a rule in the core Dart rule set
type-enhancement
A request for a change that isn't a bug
Describe the quick-fix
It would be great if any future could be passed into a
FutureOr<void>
argument. Anyway, the only reasonable thing is to await it; and passing aFutureOr<Whatever>
is already allowed.Basically remove the
&& ...
part from the rule.The text was updated successfully, but these errors were encountered: