TypeScript does not recognize unreachable code after a method returning never is called outside of its defining scope

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.89.1
• OS Version: All

To Reproduce:

class SimpleThrower {
    public throwError(): never {
        throw new Error('');
    }

    public doSomething(): string {
        this.throwError(); // Directly call the never-returning function
        
        return 'Success'; // TypeScript recognizes that this line is unreachable
    }
}

() => {
    const example = new SimpleThrower();
    console.log(example.doSomething()); // This will throw an error
    example.throwError(); // Throws an error and stops execution
    console.log('foobar'); // TypeScript does not recognize that this line is unreachable
}

Playground Link

Expected behavior:

TypeScript should recognize that the line console.log('foobar'); is unreachable after example.throwError(); is called, similar to how it recognizes the unreachable code within the doSomething method.

Actual behavior:

TypeScript does not mark the line console.log('foobar'); as unreachable after the example.throwError(); call in the global scope or within a different function scope.

提供された Playground Link から始め、外側の関数での example.throwError() 後の挙動と、this.throwError() 後の doSomething 内で到達不能なコードが認識される仕組みを比較してください。never を返すメソッドの呼び出しを担当する TypeScript の制御フロー解析のエントリポイントを追跡してください。後者の場合に console.log('foobar') が到達不能としてマークされ、既存のメソッドの挙動を後退させないことが完了条件です。