JDK-4904074 : (coll) Provide basic Map.Entry class
- Type: Bug
- Component: core-libs
- Sub-Component: java.util:collections
- Affected Version: 6
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2003-08-10
- Updated: 2017-05-16
- Resolved: 2005-09-04
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 6 |
|---|
6 b51Fixed  |
Description
Writing a Map implementation is a bit more difficult than some other collection interfaces. The task would be made easier if some assistance were provided in writing the Map.Entry implementation that all Map implementations must provide. It would make sense for java.util to provide a "basic map entry" that was simply a container for a key and a value that knew how to compute the proper equals, hashCode and toString functions. In fact, such a class already exists privately inside AbstractMap with the notation "This should be made public as soon as possible."
Comments
|