-
Notifications
You must be signed in to change notification settings - Fork 101
Comparing changes
Open a pull request
base repository: haskell-unordered-containers/unordered-containers
base: v0.2.20
head repository: haskell-unordered-containers/unordered-containers
compare: v0.2.20.1
- 9 commits
- 16 files changed
- 4 contributors
Commits on May 11, 2025
-
Make CI work again and bump to 9.12.2 (#499)
* Bump CI to GHC 9.12.2 and ubuntu-24.04 (needed) * Relax bounds for GHC 9.12 (needed)
Configuration menu - View commit details
-
Copy full SHA for 37eee22 - Browse repository at this point
Copy the full SHA 37eee22View commit details
Commits on Sep 26, 2025
-
Remove bad isSubmapOf testcase (#504)
The property tested is covered by the test case above, but the property claimed in the test name is plain wrong: m1 ⊈ m2 ⇒ m1 ∪ m2 ⊈ m1: FAIL *** Failed! Falsified (after 1 test and 2 shrinks): fromList [(K {hash = 0, _x = A},0)] fromList []Configuration menu - View commit details
-
Copy full SHA for fee3769 - Browse repository at this point
Copy the full SHA fee3769View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8e380a6 - Browse repository at this point
Copy the full SHA 8e380a6View commit details
Commits on Sep 29, 2025
-
Fix infinite loop in
isSubmapOf[By]/isSubsetOfon 32-bit platfo……rms (#501) The internal `submapBitmapIndexed` function used by these functions could enter an infinite loop while comparing two nodes `m1` and `m2` where `m2` contained a sub-node associated with the partial hash `0b11111`. In this case the high bit of the combined bitmap of `m1` and `m2`, `b1Orb2`, was `1`. After checking the submap condition at the high bit, the 32-bit `m` variable used to iterate over `b1Orb2` would be left-shifted and overflow to `0`, resulting in the infinite loop. https://github.com/haskell-unordered-containers/unordered-containers/blob/37eee2290cab287c0947d1de20235a37ced63c94/Data/HashMap/Internal.hs#L1551-L1572 To fix this bug and any similar issues related to a branching factor of 32, we return to a branching factor of 16 for 32-bit platforms. On 64-bit platforms the branching factors stays at 32. Fixes #491.
Configuration menu - View commit details
-
Copy full SHA for 0971ad5 - Browse repository at this point
Copy the full SHA 0971ad5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 333ccb3 - Browse repository at this point
Copy the full SHA 333ccb3View commit details -
Fixes docs of Data.HashMap.Lazy.fromList: it takes O(n * log(n)) (#498)
Fixes the incorrect documentation in Data.HashMap.Lazy.fromList / Data.HashMap.Internal.fromList: This takes linearithmic time rather than linear time, since we do n insertions, each of which takes (assuming no collisions!) log32(n) steps as per the documentation of insert. Fixes #309
Configuration menu - View commit details
-
Copy full SHA for 7c66911 - Browse repository at this point
Copy the full SHA 7c66911View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7310538 - Browse repository at this point
Copy the full SHA 7310538View commit details -
Add disclaimer to D.HS.toList (#507)
...and improve the disclaimer for D.HM.toList. Fixes #481.
Configuration menu - View commit details
-
Copy full SHA for 5cdf332 - Browse repository at this point
Copy the full SHA 5cdf332View commit details
Commits on Oct 2, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 64e342e - Browse repository at this point
Copy the full SHA 64e342eView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.20...v0.2.20.1