Spurious "referenced directly or indirectly in its own initializer" when combined with narrowing, asserts function, and loop

Bug Report

🔎 Search Terms

referenced directly or indirectly asserts

🕗 Version & Regression Information

• This is the behavior in every version I tried

⏯ Playground Link

Playground Link

💻 Code

declare const myRequire: ((p: string) => {} | undefined) | undefined;

declare function assertIsDefined<T>(value: T): asserts value is NonNullable<T>

function fn1() {
    if (!myRequire) {
        return;
    }

    for (const p of ["a", "b"]) {
        // Error?
        const result = myRequire("something");
        assertIsDefined(result);
    }
}

🙁 Actual behavior

result is claimed to be referenced directly or indirectly in its initializer.

Modifying the code in various ways makes the error go away.

🙂 Expected behavior

No error; there's no relationship between the initializer and the result.

Commencez par le TypeScript Playground lié et exécutez l’exemple de code fourni pour reproduire le diagnostic. Examinez la gestion par le compilateur du narrowing, des asserts functions et de la boucle autour de l’initializer. Le travail sera considéré comme terminé lorsque l’exemple ne signalera plus que result est référencé dans son propre initializer, tout en conservant le comportement de narrowing attendu.