Inlay hints should display inferred type argument

[Zekfad]

Is your feature request related to a problem? Please describe.
It's hard to navigate to inferred type of generics. You have to lookup relevant argument and find type from it.
For now it's only possible to see inferred type from hover popup, but it's just plain text.

Describe the solution you'd like
Inlay hints should show clickable inferred types of generics.

Describe alternatives you've considered
Make hovers interactive? (But that's likely out of scope).

Additional context

Screenshot of current behavior

[DanTup]

Do you mean in cases like this?

foo<T>(T a) {
  foo('');         // Show an inlay hint of `<String>` after `foo` so this reads foo<String>('')
}

[Zekfad]

Hi @DanTup, thanks for fast reply, yes, that's what I meant.

[DanTup]

I've a change open to add this for type arguments and also list/map/set literals where it was missing before.

https://dart-review.googlesource.com/c/sdk/+/284143

[Zekfad]

Hi @DanTup, thank you for your work!
Is there ETA for Preview version with this feature?

On your screenshot, it infers <int>a: [1,2], shouldn't it be a: <int>[1,2]?

[DanTup]

The change is in the Dart analysis server in the SDK, so once the review is done and the code landed, it'll be available in main channel builds of the SDK usually within a few hours or so (and Flutter's master branch probably within a few days). I wouldn't recommend using those versions for production work but they're good for testing. Of course the change will also then show up in future dev/beta/stable releases of the SDKs.

[DanTup]

Landed in dart-lang/sdk@e8a8e10.

[Zekfad]

Hi @DanTup, on your screenshot, it infers <int>a: [1,2], shouldn't it be a: <int>[1,2]?

[DanTup]

@Zekfad Oof, yes, I hadn't noticed that (and apparently I didn't write tests when there are both type args and parameter names at the same offset). I will fix, thanks!