Comment is not infered correctly when using generic type

Bug Report

🔎 Search Terms

generic comment

🕗 Version & Regression Information

4.4.2

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

⏯ Playground Link

https://www.typescriptlang.org/play?ts=4.4.2#code/JYOwLgpgTgZghgYwgAgKoGdrIN4ChkHID0AVCfocicgLICeyAwgPYC2rE4yAEtBAHSCKhEkWHIQcDgC5k6MFFABzXAF9cuIkWQBRAB4AHCAkgATTdoDqAC07IEAVyjpmUZMHTJmIZAHJJHL4ANPZsHFzMMH4BEL7IcAZGcFAQ5jAOICbA3sjpmQCMABQOmFCyGNAAlDjqeQhFeJQxsr4AGu2+apUaWmggEIbGZhbINnaOzq7unjn+UrEhIMyh7Jxg8YkQyam4dWDZPnUATAA8ACrIA5Agpp4VUAB8xaWyZ9XYtRkIR4WNhM1+dqtTqqSpAA

💻 Code

interface User {
    /**
     * My Comment Here...
     */
    name: string
}

// Expected
// When cursor is on 'name', comment of 'name' appeared
function func1(user: User) {}
func1({
    name: 'XXX'
})

// Unexpected
// When cursor is on 'name', no comment appeared
function func2<T extends User>(user: T) {}
func2({
    name: 'XXX'
})

🙁 Actual behavior

No comment for func2

🙂 Expected behavior

Show comment for func2

Beginne mit dem verknüpften TypeScript 4.4.2 Playground-Repro und vergleiche die Kommentar-Inferenz für func1 und generisches func2. Verfolge die Kommentarsuche für die name-Eigenschaft in beiden Beispielen und überprüfe anschließend, dass der generische Aufruf wie erwartet „My Comment Here...“ anzeigt.