require-atomic-updates reports false positive when the assigned variable is used in a lambda and function call

[Liu233w]

Tell us about your environment

I've built a simple example in ESLint Demo, my configuration is included in it.

• ESLint Version:
  6.0.1

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

{
    "parserOptions": {
        "ecmaVersion": 9,
        "sourceType": "script",
        "ecmaFeatures": {}
    },
    "rules": {
        "require-atomic-updates": 2
    },
    "env": {}
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

async function main() {
  let a = someFunc()
  a(()=>a) // change it to `f(()=>a)`, `a(a)` or `a(()=>b)` will all pass the lint
  a = await func() // Possible race condition: `a` might be reassigned based on an outdated value of `a`.
}

What did you expect to happen?
Pass without error

What actually happened? Please include the actual, raw output from ESLint.
Possible race condition: a might be reassigned based on an outdated value of a.

[mysticatea]

Thank you for your report.

In fact, as based on the discussion in #11774, this is intentional behavior. ESLint cannot know when ()=>a function will be called, so the rule handles it as a possible race condition.

[Liu233w]

Thank you for your reply, @mysticatea .

According to the discussion, statements like f(()=>a) should also be marked as a possible race condition. But in the demo above, only a(()=>a) is reported, while f(()=>a) does not. Is that an intended behavior?