strager
```js for (;;) { class C { static { break; // should error } } } ```
Comparing against NaN with `==` or `===` will always return false: ``` null == NaN // false NaN == NaN // false 0 == NaN // false Infinity == NaN...
(and maybe other pages) Possible cause: 1-second expiration? etags seem to work for other files such as /dusty.svg.
https://developers.google.com/search/docs/advanced/appearance/sitelinks Currently, Google shows the feature comparison table. It looks ugly. Let's coerce Google into showing nav instead.
```js class C { async static f() {} // error static public g() {} // no error, but should async async async async h() {} // no error, but should...
```js switch (a) { case "one": break; case "one": // warning break; case "three": break; } ```
```js let o = { foo() {}, foo: 42, // warning }; ```
```js class C { foo() {} foo() {} // warning } ```
`x! == y` is legal TypeScript but might have been a typo for `x !== y`. Issue a warning, suggesting parentheses around `x!` if a null assertion was intended. Note:...
`!"key" in obj` is the same as `false in obj`, which is probably unintended. Warn on `in` where the left-hand side is `!` followed by a literal (number or string...