Skip to content

fix TypeParameterMember equality #27210

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.

Sign up for GitHub

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

Jump to bottom
Closed
jmesserly opened this issue Aug 31, 2016 · 1 comment
Closed

fix TypeParameterMember equality #27210

jmesserly opened this issue Aug 31, 2016 · 1 comment
Labels
legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on

Comments

@jmesserly
Copy link

I'm about to land a patch that adds some equality support to TypeParameterMember: https://codereview.chromium.org/2291103004/

However it does not handle the bound correctly. In general we don't track the bounds of type parameters very well and this bug is hit in several places in strong mode. Also related to #27040 which we'd like to fix.

Found wile working on #25740 (comment)
@jmesserly jmesserly added legacy-area-analyzer Use area-devexp instead. analyzer-strong-mode P2 A bug or feature request we're likely to work on labels Aug 31, 2016
@jmesserly jmesserly self-assigned this Sep 29, 2016
@jmesserly
Copy link
Author

https://codereview.chromium.org/2375103004/

@jmesserly jmesserly removed their assignment Oct 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jmesserly