noImplicitAny ignored on generic type resolution

[markoknez]

TypeScript Version: 3.6.2

Search Terms:
noImplicitAny generic

Code

class Test<T> {
    options: Map<T, string> = new Map()
    constructor(options: Map<T, string>) {
        
    }
}

let t = new Test(new Map())
t.options.set("a", "abc")
t.options.set(123, "abc")

Expected behavior:
When using strict / noImplicityAny I would expect that T which implicitly became any would be reported as an error.

Actual behavior:
No error thrown, T becomes of type any.

Playground Link:
https://www.typescriptlang.org/play/index.html?target=6#code/MYGwhgzhAEAqCmEAuAeWA+aBvAUNf0A9gA5ICWhAdhAFzQCyYxaANNMgE5mUDmmAvNErwA7gyYAKAJR4CwKpwCuwJIQ4SS5BXUbNYbTtz5TssggTPQAvjhs4Q8JNCeDhYhMglvxxaTKQAdJoU1AEQjhIARGCRbNEARsCR-kGkIRBhEQCMAEwAzHFgiclAA

[RyanCavanaugh]

This doesn't fit the criteria of an "implicit any". Map explicitly has a construct signature that returns Map<any, any>, and that first any was an explicit inference candidate for Test<T>'s T.

Relevant discussion at #24737

[typescript-bot]

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.