Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 14 commits
- 10 files changed
- 1 contributor
Commits on Aug 27, 2024
Commits on Aug 28, 2024
-
-
-
Merge pull request #341 from cuviper/from-entry
Implement `From` between `IndexedEntry` and `OccupiedEntry`
-
Merge pull request #342 from cuviper/btree-like
Add a few nods to `BTreeMap`/`Set`
-
Commits on Aug 30, 2024
-
Use
insert_beforefor "new" entries ininsert_sortedThe only difference compared to using `shift_insert` is when the binary-searched key isn't *actually* new to the map, just not found in properly sorted order. In this case we can't guarantee a sorted result either, but it will at least behave better about the new position, especially if that's the end.
-
-
Merge pull request #340 from cuviper/insert-bounds
Assert bounds in `shift_insert` and add `insert_before`
-
Loading
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 2.4.0...2.5.0