Ryan Cavanaugh

Removing anything that might possibly be a red herring: ```ts repro interface StringType { prop: string } interface UnknownType { prop: unknown } interface ResultOne { type: "one"; value: G["prop"];...

This is the syntax you would use to describe an object which is callable both with and without `new`, which is a thing that people do in JS sometimes.

The failure here is saying that this change causes TS to no longer be able to build itself. Confirming, I see this locally checking out your PR branch, but not...

Aside, it's quite rare to break TS without affecting any other tests! We'd want a testcase that isolates the problem this exposes, assuming there is one.

Interesting case. Right now this check is *almost* entirely syntactic; it does consider exhaustive `switch`es but otherwise doesn't use CFA types at all. This is probably a Won't Fix unless...

@typescript-bot pack this

@andrewbranch fyi in case you can do this quickly and want to

There's only one answer that results in no errors, right? I think I'm missing something

https://github.com/microsoft/TypeScript/issues/44457#issuecomment-856170640

Well, I think we kind of messed up with `noImplicitOverride` under `abstract` and need to figure out what to do next. The intent of the flag, at least in my...