Bug Report

🔎 Search Terms

union generic implicit

🕗 Version & Regression Information

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

⏯ Playground Link

Playground link with relevant code

💻 Code

interface TwoSameTypes<T> {
  a: T;
  b: T;
}

// @ts-expect-error
const x : TwoSameTypes<Number | String> = {
  a: 1,
  b: "string", // <-- This does not give an error, because `b` has the type `String | Number`
}

🙁 Actual behavior

No error happens

🙂 Expected behavior

I would expect an error for the value of x because both a and b are expected to have the same type, but they don't in this case.

For the record, and as can be seen from the playground link, when doing TwoSameTypes<Number> | TwoSameTypes<String> instead of TwoSameTypes<Number | String> we do end up with the desired behaviour. But I think these two different ways of defining are equivalent? So it seems like the latter way of doing it should work as well.

Furthermore, here's demo of a use case for this behaviour. I would like to use keyof ValueMap as the generic type, so I don't have to type every possible enum twice.

Apologies in advance if this is a duplicate, I wasn't able to find the right keywords to describe this behaviour.