JDK-8013150 : Iterator.remove and forEachRemaining relationship not specified
- Type: Bug
- Component: core-libs
- Sub-Component: java.util
- Affected Version: 8
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-04-24
- Updated: 2014-03-21
- Resolved: 2013-05-07
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 8 |
|---|
8 b91Fixed  |
Related Reports
|
Relates :
|
Description
After forEachRemaining returns a subsequent remove() should remove the last element and not throw an exception. The default implementation on Iterator removes the last element, and optimized implementations of the default should remain consistent. Also check other ListIterator methods such as previous() and set().
Comments
|