Certain conditional types allow unsound assignments

🔎 Search Terms

"conditional type" generic assignment

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about conditional types

⏯ Playground Link

https://www.typescriptlang.org/play?#code/C4TwDgpgBAQg9gDwDwBUB8UC8UDeUBuAhgDYCuEAXFClAL4BQ9okUAqgHYBGiAku+xABOqDNhoQEwCOwAmAZ1iIkAS3YAzIVABKGAPxsuvfkKQ6oVPKUMIIMqjQbNoHbsnRYDrvgOHoA2gDkVq62AQC6jDIQAMbEhILQalbRwMpw7FDBSugAFAj2AJRULtlojEnsKWkZEoQAtmDEECJ5hbj0UFBNwFCEHlkIeQUdvR4BwAAWygpyE3CkxDJQnNCENYKCcIIB9LRAA

💻 Code

type Box<T> = { value: T }

type UnboxInner<T> = T extends Box<infer R> ? UnboxInner<R> : { unboxed: T }
type Unbox<T> = UnboxInner<T>['unboxed']

declare function unbox<T>(x: T): Unbox<T>

function example<T>(x: T) {
  let a = unbox(x)
  a = 'this should be an error'
}

🙁 Actual behavior

In example we can assign arbitrary values to a, even though it's typed as Unbox<T>.

🙂 Expected behavior

Attempting to assign invalid values to a (just about anything, since its type depends on a type parameter) should cause a type error.

Additional information about the issue

These issues may possibly be related:

• #52021
• #35533

cc @webstrand

Commencez par la reproduction liée dans TypeScript Playground et comparez le comportement avec les issues associées #52021 et #35533. Suivez la vérification des affectations génériques de types conditionnels dans le compilateur TypeScript ; le travail est terminé lorsque l’affectation montrée est rejetée et qu’un test de régression couvre le comportement.