Ryan Cavanaugh

Bisects to #55941

cc @Andarist - any thoughts? Should we revert that PR?

@Andarist is right - this code isn't really distinguishable from code that is removing `name` on purpose We can't warn every time any possible thing happens.

Why isn't `TypeB` written this way? ```ts type TypeB = { kind: MyEnum.B; } & ({ id?: number | undefined; }); ```

Bisects to #53709

TypeScript 4.9 is 18 months old - can you please try on latest?

This might be an issue with the types in one of those dependencies. Please provide a reduced (isolated) repro -- it's really not possible to look at that target type...

@weswigham probably worth taking another look at the linked PR and seeing what we might do here

@ahejlsberg this is a co-effort with @jack-williams that looks very promising. Thoughts?

> Was this partially enabled by #43183? No. This issue is about value narrowings causing follow-on effects to how we reason about the type parameters themselves.