<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section! Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ Please fill in the *entire* template below. --> <!-- Please try to reproduce the issue with the latest published version. It may have already been fixed. For npm: `typescript@next` This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly --> **TypeScript Version:** 4.0.0-dev.20200720 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** **Code** For the typescript ```ts /** @deprecated */ function bar(x: number, y: number){} bar(1, 2); export interface Foo { /** @deprecated */ bar(x: number, y: number): void; } ({ } as Foo).bar(1, 2); ``` **Expected behavior:** I'd expect that just the function and method names (`bar`) are marked as deprecated **Actual behavior:** The entire call expression is marked as deprecated <img width="715" alt="Screen Shot 2020-07-21 at 12 17 18 AM" src="https://user-images.githubusercontent.com/12821956/88024438-8bcdd500-cae7-11ea-8ff8-213c832b194c.png"> For complex function/method calls, the current behavior feels a little too agressive : <img width="1676" alt="Screen Shot 2020-07-21 at 12 19 15 AM" src="https://user-images.githubusercontent.com/12821956/88024605-d94a4200-cae7-11ea-825f-24db90925696.png">