JDK-8196074 : Remove uses of loose type equality tests
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-01-24
  • Updated: 2018-02-16
  • Resolved: 2018-01-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11
11 b01Fixed
Related Reports
Duplicate :  
JDK-8162803 - investigate type containment, type equality and their relationship
Description
Since Java SE 8, javac has two ways of performing equality tests: a loose one (the historical one) and a stricter one (closer to JLS) which was necessary to have in order a sound implementation of the new inference scheme.

As the compiler implementation was progressively refined, we should try and get rid of remaining uses of the loose equality check.

See:
http://mail.openjdk.java.net/pipermail/compiler-dev/2018-January/011593.html