Skip to content
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

Improve ordering and de-duplication of category method completion proposals #1153

Closed
eric-milles opened this issue Aug 14, 2020 · 1 comment
Assignees
Milestone

Comments

@eric-milles
Copy link
Member

When multiple options exist for a given method completion, like find(Iterable) and find(Object), ordering and de-duplication do not take into account the best match for the receiver type. For example, when the completion type is a List, there is a findAll extension method for List and a more general one for Collection. Only one is proposed for completion and at the moment they are assigned equal relevance, so the last one declared in the one proposed.

image

@eric-milles
Copy link
Member Author

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant