Make Type Hints less intrusive

[psfinaki]

So this is quite annoying:

2022-11-23.19-29-32.mp4

Instead, I'd prefer the behavior like in C# on the right - show the type when we can provide useful information (e.g. when the equal sign is printed).

[psfinaki]

We had a brief session on this with @vzarytovskii - but our best idea so far is just to look if there are any diagnostics within the range, like don't show any hints if there is an error in the code. Seems a bit crude but better than the current situation.

@dsyme @T-Gro @kerams Maybe you have any ideas?

[kerams]

Here the typar of b is unsolved. Since incomplete bindings like that seem to be assigned placeholder generic type variables, mayhaps it would be a good rule of thumb not to show generic type hints unless they are solved (which the type of the value a above is)?

[T-Gro]

I would not couple it with diagnostics - there might be diagnostical errors which work just fine with type hints.
Instead I would prevent showing useless information => if a type cannot be derived, the hint is not telling much.

[psfinaki]

Well the problem with this is that this info seems to be buried very deep in the symbol and it will take some effort to propagate it properly. But I'll give it a try.

Or I just cannot find a better way :D But at least the property IsUnresolved returns false in both cases which was my hope at first.

[0101]

Could we somehow get the hint to be on the other side of the cursor? I think that would help no only this case but usability in general.