[YANGTOOLS-563] Mutable/ImmutableOffsetMap do not conform to their promised contract Created: 17/Dec/15 Updated: 10/Apr/22 Resolved: 08/Jan/16 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4803 |
| Description |
|
The current implementation does not correctly retain iteration order, even though it promises to do so (and is used in those contexts). Furthermore the implementation retains KeySet from the original map if such a mapping does not exist. And the .equals() implementation does not conform to Map.equals() contract. |
| Comments |