Inferred type is not the same as what's passed in original generic type.

Bug Report

🔎 Search Terms

infer, generic

🕗 Version & Regression Information

• This is a crash
• This changed between versions _________ and _________
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about infer.
• I was unable to test this on prior versions because _______

⏯ Playground Link

https://www.typescriptlang.org/play?ts=4.1.3#code/C4TwDgpgBACgTgezAYQQOwM7DgVwMbAJwA8AKlALxQCGaIAfJQFBRQA+UA3lGhAO5QAFADpR1OAHMMALhp0A2gF0AlLPIAyKAgBGAKwgEoAXxbsuQ1VHImmoSFACyIAJJoAZhBKlGVchAAewBBoACYYsIgo6Fi4BETEAJbunlAAaowA-GlQsgDk-gW5TLbg0KnllEKCypSMMUkSNRyC1bU8OAC22p7KxXbQABqVTq4eJPBIqJjY+IQk5en0TEA

Playground link with relevant code

💻 Code

// The variable names are meaningless, they are simplified from vue project.
type PropConstructor<T = any> =
  | { new (...args: any[]): T & object }
  | { (): T }

type MyInfer<T> = T extends PropConstructor<infer V> ? V : 'xxx'

type VVV = (() => string) | (() => number)

type X = MyInfer<PropConstructor<VVV>>

🙁 Actual behavior

type X = (() => string) | (() => number) | ((() => string) & object) | ((() => number) & object)

🙂 Expected behavior

type X = (() => string) | (() => number))

Inizia eseguendo gli esempi collegati di TypeScript Playground e confrontando il tipo inferito X con i tipi effettivo e previsto riportati. Il lavoro è completo quando il comportamento dell’inferenza generica per MyInfer<PropConstructor> corrisponde all’unione prevista senza le intersezioni aggiuntive.