-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Add discarded_futures #74
Comments
After some reasearch, seems like there are some unresolved false positives issues with this rule. Dealing with false positives is the biggest blocker for this issue to be added to VG analysis IMO |
With this issue being open for over a year and no new comments, along with Dart issues still being open on it, closing this out as a won't fix. If this should be re-addressed in the future feel free to open another issue with updated information. |
Description
Making asynchronous calls in non-async functions usually signals a programming error. These functions should generally be marked async, and such futures should probably be awaited (as enforced by unawaited_futures).
So, to avoid this kind of problem, it would be really nice to have the
discarded_futures
included in the analysis.Documentation
The text was updated successfully, but these errors were encountered: