JDK-8162108 : Rename weakCompareAndSetVolatile to weakCompareAndSet
- Type: Sub-task
- Component: core-libs
- Sub-Component: java.lang.invoke
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-07-21
- Updated: 2017-05-17
- Resolved: 2016-09-01
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.
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 9 |
|---|
9 b135Fixed  |
Description
Rename weakCompareAndSet to weakCompareAndSetPlain and weakCompareAndSetVolatile to weakCompareAndSet, thereby leveraging a consistent naming scheme for read-modify-write methods. The Atomic* classes should be updated in a separate issue to: 1) deprecate (not for removal) weakCompareAndSet 2) add weakCompareAndSetPlain, and leave weakCompareAndSetVolatile (which remains the sole inconsistency in the naming scheme)