Extend "no comparison with NaN" check to cover "Number.NaN"

Suggestion

🔍 Search Terms

x === Number.NaN
disallow comparing with Number.NaN

✅ Viability Checklist

My suggestion meets these guidelines:

• [?] This wouldn't be a breaking change in existing TypeScript/JavaScript code - this would break code containing the error
• ✅ This wouldn't change the runtime behavior of existing JavaScript code
• ✅ This could be implemented without emitting different JS based on the types of the expressions
• ✅ This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• ✅ This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Extend check added for https://github.com/microsoft/TypeScript/issues/49962 to include Number.NaN in addition to global NaN.

📃 Motivating Example

function useVersionNumber(value: string) {
    let versionNumber = Number(value);
    if (versionNumber === Number.NaN) {
        return;
    }
    console.log(versionNumber + 1);
}

💻 Use Cases

Catching a developer error (incorrect NaN handling).

Lies den bestehenden, in Issue #49962 referenzierten Check und finde seine Implementierung und Tests im TypeScript-Repository. Erweitere dasselbe Verhalten auf die Form Number.NaN und überprüfe anschließend, dass der zugrunde liegende Vergleich gemeldet wird, während die JavaScript-Ausgabe zur Laufzeit unverändert bleibt.