Union type in element access can prevent deprecated warning from triggering

TypeScript Version: 4.1.0-dev.20201027

Search Terms: Deprecated tag, union, element access

Code

const foo = {
    faff() { },

    /** @deprecated */
    fluff() { }

}

declare const k: "faff" | "fluff";

//Expected: deprecation warning
//Actual: no warning
foo?.[k]?.();

const bar = {
    /** @deprecated */
    faff() { },

    fluff() { }
}

//Expected: deprecation warning
//Actual: deprecation warning
bar?.[k]?.();

Expected behavior:

foo?.[k]?.(); should show deprecated warning because if k is "fluff", then we'll be calling a deprecated method.

Actual behavior:

foo?.[k]?.(); has no deprecated warning.

Playground Link: Playground

Related Issues: Couldn't find any

Start with the linked TypeScript Playground reproduction and compare the foo?.[k]?.() and bar?.[k]?.() cases using the reported TypeScript version. Trace how deprecated warnings are produced for optional element access with union keys; done means the foo case reports a deprecation warning without regressing the existing bar case.