Skip to content

Try to avoid overconstraining when comparing and/or types #230

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 3 commits into from
Nov 18, 2014

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Nov 16, 2014

Review by @smarter

See comments in eitherIsSubType for an explanation what the
problem is. Some test cases are in subtyping.scala
class A {
def test1(): Unit = {
implicitly[this.type <:< this.type]
implicitly[this.type <:< A]
Copy link
Member

Choose a reason for hiding this comment

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

Why did you remove these tests?

@smarter
Copy link
Member

smarter commented Nov 18, 2014

LGTM.

@odersky
Copy link
Contributor Author

odersky commented Nov 18, 2014

Thanks for the review!

odersky added a commit that referenced this pull request Nov 18, 2014
Try to avoid overconstraining when comparing and/or types
@odersky odersky merged commit 7a1f630 into scala:master Nov 18, 2014
@allanrenucci allanrenucci deleted the fix/and-or-subtyping branch December 14, 2017 19:21
WojciechMazur pushed a commit to WojciechMazur/dotty that referenced this pull request May 8, 2025
Backport "Remove DRI from Scaladoc warnings" to 3.3 LTS
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.

2 participants