Skip to content

[analyzer] Implicitly tear off call from receiver whose type is a type variable #54353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
eernstg opened this issue Dec 14, 2023 · 2 comments
Closed
Assignees
Labels
dart-model-analyzer-spec Issues with the analyzer's implementation of the language spec legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on

Comments

@eernstg
Copy link
Member

eernstg commented Dec 14, 2023

This is the analyzer specific issue for #54351 which has the details.

@eernstg eernstg added legacy-area-analyzer Use area-devexp instead. dart-model-analyzer-spec Issues with the analyzer's implementation of the language spec labels Dec 14, 2023
@bwilkerson bwilkerson added the P2 A bug or feature request we're likely to work on label Jan 5, 2024
@bwilkerson
Copy link
Member

@scheglov

@scheglov
Copy link
Contributor

class A {
  void call() {}
}

Function f<X extends A>(X x) => x;

We might not do rewrite to ImplicitCallReferenceImpl for => x.
IIRC, @srawlins started adding such rewrites, but we did not have time to do it everywhere.
I also will not have time to do this short term.

@srawlins srawlins self-assigned this Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dart-model-analyzer-spec Issues with the analyzer's implementation of the language spec legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on
Projects
None yet
Development

No branches or pull requests

4 participants