Some types are incorrectly assignable from a generic distributive conditional type

TypeScript Version: 3.5.1

Search Terms: generic conditional distributive assignable from

Code

type Keys<T extends object> = T extends unknown ? keyof T : never;

function f<T extends object>(keys: keyof T, moreKeys: Keys<T>) {
    keys = moreKeys;
}

// With this instantiation, `keys` is typed 'a',
// and `moreKeys` is typed 'a' | 'b' | 'c'. The latter
// should not be assignable to the former, but it happens
// in the generic context of the function `f`.
f<{ a: any, b: any } | { a: any, c: any }>('a', 'b');

Expected behavior:

Keys<T> should not be assignable to keyof T since Keys<T> is distributive and will produce a different type than keyof T when T is a union type.

Note that the reverse of this assignment, moreKeys = keys, errors for this exact reason; without a concrete T, it’s hard to tell what the relationship should be, so we simply have no relationship in place.

Actual behavior:

The unsafe assignment is allowed.

Playground Link

Start by reproducing the generic distributive conditional-type example in the linked Playground. Trace the type-checking path for assignability in the generic context, then add a regression test covering the unsafe assignment and the stated reverse-assignment behavior. Done means the call with 'b' is rejected because Keys is not assignable to keyof T.