I support the proposal to ignore IIFEs, and I think there's no need for an option (the issue title suggests adding an option).

However, named function expressions could be stored so perhaps we should additionally check if the function is referenced.

let current = getStart();
const arr = [];
while (current) {
  (function f() {
    current;
    arr.push(f); // <--
  })();
  
  current = current.upper;
}

I support the proposal to ignore IIFEs, and I think there's no need for an option (the issue title suggests adding an option).

However, named function expressions could be stored so perhaps we should additionally check if the function is referenced.

I think we should also keep reporting on IIFEs with async and generator functions, because their asynchronous state may become accessible from outside, even without a self-reference.

let current = getStart();
const arr = [];
while (current) {
  const p = (async () => {
    await someDelay();
    current;
  })();

  arr.push(p);
  current = current.upper;
}
await Promise.all(arr);

Other that this (and possibly other yet-to-be-discovered edge cases), I also like the proposal.

Oops! It looks like we lost track of this issue. What do we want to do here? This issue will auto-close in 7 days without an update.

In the 2023-03-23 TSC meeting we have agreed to:

1. Accept the proposal
2. Not add an option and instead make this change a default behavior
3. Continue warning in the async/generator case

Notes from this meeting will be published in this PR.

Would love to work on this.

Apparently, we should also ignore reporting for this rule, if the function is called (irrespective of its IIFE nature) anywhere inside the loop's scope.