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
singleton type pattern should use eq
, not ==
for test
#4577
Comments
Imported From: https://issues.scala-lang.org/browse/SI-4577?orig=1 |
@paulp said: |
@paulp said: |
@paulp said: |
@paulp said: https://issues.scala-lang.org/secure/IssueNavigator.jspa?mode=hide&requestId=12202 |
@gkossakowski said: |
@adriaanm said: |
@paulp said: |
@adriaanm said: |
Stephen Compall (s11001001) said: |
@adriaanm said: |
GI intend to conquer the pattern matcher this time. Have to do some ticketizing.
The following test case reveals multiple significant issues with equality, including calling equals when it's supposed to be using reference equality, and considering a stable identifier
foo
to be unreachable on the basis that _: foo.type had not matched. (It can actually learn nothing, because the one should be reference equality and the other should be a call to equals.)The text was updated successfully, but these errors were encountered: