Skip to content

Fix #6724: Don't suggest types for terms and vice versa #6735

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

Merged
merged 2 commits into from
Jun 24, 2019

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jun 24, 2019

Filter candidate definitions for member suggestions to be either types or terms,
depending on the selection name.

odersky added 2 commits June 24, 2019 14:41
Filter candidate definitions for member suggestions to be either types or terms,
depending on the selection name.
@odersky odersky merged commit 1268474 into scala:master Jun 24, 2019
@allanrenucci allanrenucci deleted the fix-#6724 branch June 24, 2019 14:31
@@ -14,8 +14,8 @@ val res0: scala.collection.mutable.ListBuffer[Int] = ListBuffer(1, 2, 3)
scala> import util.foo
1 | import util.foo
| ^^^
| value foo is not a member of util - did you mean util.Left?
| value foo is not a member of util - did you mean util.Try?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you explain this one to me? import util.Left is invalid? Or did it change because Try has a higher priority on the list of suggestions?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or did it change because Try has a higher priority on the list of suggestions?

Something like that yeah. Ideally it should just not offer any suggestion at all when there's nothing close to what the user has written.

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

Successfully merging this pull request may close these issues.

3 participants