IntSet.deleteMin doesn't agree with Set.deleteMin
(!IntSet.deleteMin !IntSet.empty) is error, while (Set.deleteMin Set.empty == Set.empty). Set and !IntSet should have identical behavior whenever possible (so that Set Int can be replaced by !IntSet without introducing bugs).
Since !IntSet.deleteMin is newer, presumably it should be changed to agree with Set.deleteMin.
The same issue applies to !IntSet.deleteMax, (snd . !IntSet.deleteFindMin), and (snd . !IntSet.deleteFindMax). Also Data.!IntMap.
This behavior was introduced in ticket 1229.
Trac metadata
| Trac field | Value |
|---|---|
| Version | 6.8.1 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | libraries (other) |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Multiple |
| Architecture | Multiple |