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
require-atomic-updates reports false positive in finally block #11954
Comments
Thank you for your report. Indeed, this is false positive. The rule checks read-update-write which is across |
Thanks for confirming the bug and for the explanation of why it is happening. |
Unfortunately, it looks like there wasn't enough interest from the team Thanks for contributing to ESLint and we appreciate your understanding. |
How about this #13915? |
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using? default
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
What did you expect to happen?
No error reported.
What actually happened? Please include the actual, raw output from ESLint.
This looks like a false positive to me. I don't see why line 19 (the
count -= 1
in thefinally
block) would use an outdated value ofcount
.Is this the intended behavior of this rule? If so, what is the race condition here?
Are you willing to submit a pull request to fix this bug?
Possibly.
The text was updated successfully, but these errors were encountered: