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

Meta-bug: Omitting non-ambiguous implicit conversions should be valid #5592

Closed
scabug opened this issue Mar 21, 2012 · 6 comments
Closed

Meta-bug: Omitting non-ambiguous implicit conversions should be valid #5592

scabug opened this issue Mar 21, 2012 · 6 comments

Comments

@scabug
Copy link

scabug commented Mar 21, 2012

The language description of implicits suggests a conjecture: omitting an implicit should be valid, unless it is ambiguous or a more specific implicit would be selected; however, due to bugs in type-inference, this is not the case.
Is the conjecture intended to hold?

I would like to collect bugs affecting this issue as related to this.

@scabug
Copy link
Author

scabug commented Mar 21, 2012

Imported From: https://issues.scala-lang.org/browse/SI-5592?orig=1
Reporter: @Blaisorblade
Affected Versions: 2.9.1

@scabug
Copy link
Author

scabug commented Apr 8, 2012

@Blaisorblade said:
Reassigning to Scala Reviewer, since my assignment apparently was not so helpful.

@scabug
Copy link
Author

scabug commented May 7, 2012

@hubertp said:
We use components/labels to carry meta information now.

@scabug
Copy link
Author

scabug commented May 8, 2012

@Blaisorblade said:
I disagree. This is a bug waiting for confirmation, not just a way to group other bugs (that was only an additional point).
I propose a conjecture, but it is not clear at all if this conjecture is intended to hold. Or rather, it seemed obvious to me until I tried locating this in the specification, and failed miserably.

If it is intended to hold, shouldn't it be added to the specification, maybe with a warning?

@scabug
Copy link
Author

scabug commented May 8, 2012

@hubertp said:
In that case this is invalid as well. This would rely on having a complete specification for the type inference which is not going to happen in the near future, otherwise it wouldn't make sense, right?
Also, specification aside "bugs in type-inference" are not necessarily bugs but often limitations of the current local type inference.

@SethTisue
Copy link
Member

stale. probably better as a discussion on https://contributors.scala-lang.org anyway, if someone is still interested

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

3 participants