Higher order functions always autocomplete to anonymous closures

Seen behavior:

Given the following code:

String _commaJoin(String x, String y) => '$x, $y';

void foo() {
  final List<String> bar = <String>['Hello', 'world'];
  bar.re**CURSOR HERE**
}

If I select ‘reduce()’ from the suggestions it will autocomplete bar.reduce((value, element) => null) highlighting null.

What I expected

What I actually wanted was bar.reduce(_commaJoin). It’s a bit of a hassle to delete the closure. In this case no autocomplete of the argument would be better, or a dropdown list of functions in the current context that match the needed signature like so:

┌─────────────┐
│ Lambda      │
│ _commaJoin  │
└─────────────┘

[gaaclarke]

Filed at https://github.com/dart-lang/sdk/issues/46979

[DanTup]

@gaaclarke just copying the above is fine, those triaging issues in the Dart repo will know what to do with it - though feel free to post the link back here (@bwilkerson who commented above is on the Dart Team and works on the analyzer).

And FWIW it’s certainly not an issue to raise issues here first if you’re unsure where they belong - there’s a fairly blurry line between what comes from server/extension, and for some smaller (or LSP) issues I’ll work on fixes too. Thanks!