De-dupe completion suggestions

[bmewburn]

Sometimes there are multiple definitions in a workspace for the same type name. An example is when stub definitions are included in the workspace to supplement code that is written in a way that makes it difficult/impossible for static analysis engines to discover (eg Laravel and laravel-ide-helper). Only offer a single completion suggestion per nae in such cases.

[KapitanOczywisty]

This is only for classes, right?

[bmewburn]

Types, functions, constants to start with. I've seen it happen with methods too.

[KapitanOczywisty]

Are you planning to compare parameters/return (for functions) or value (for constants) to merge only the same definitions? Besides user-land collisions there is also #737

[bmewburn]

For completions I'm thinking that it is better to show just a single entry if the insert text is the same but show a doc section for both definitions. For example, with strtr it will always auto complete as strtr(|) even though there is two signatures.

[bmewburn]

functions, constants, type de-duped in 1.3.3. Leaving open to investigate members.

[KapitanOczywisty]

Will extension select compatible signature by itself? For now it always shows first one.

How this work in TypeScript:

Btw. I'm hyped about implementing this for methods too :)

[bmewburn]

@KapitanOczywisty , I opened #933 for this.