| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-04-23 | liballoc: more compact way to adjust test sizes for Miri | Ralf Jung | -36/+18 | |
| 2020-04-06 | Use usize::MAX as assoc const in liballoc | Linus Färnstrand | -1/+1 | |
| 2020-04-01 | Rollup merge of #68770 - ssomers:btree_drain_filter, r=Amanieu | Dylan DPC | -1/+339 | |
| BTreeMap/BTreeSet: implement drain_filter Provide an implementation of drain_filter for BTreeMap and BTreeSet. Should be optimal when the predicate picks only elements in leaf nodes with at least MIN_LEN remaining elements, which is a common case, at least when draining only a fraction of the map/set, and also when the predicate picks elements stored in internal nodes where the right subtree can easily let go of a replacement element. The first commit adds benchmarks with an external, naive implementation. to compare how much this claimed optimality-in-some-cases is actually worth. | ||||
| 2020-03-30 | fix BTreeMap test compilation with Miri | Ralf Jung | -1/+1 | |
| 2020-03-29 | BTreeMap/BTreeSet: implement and test drain_filter | Stein Somers | -1/+339 | |
| 2020-03-28 | BTreeMap testing: introduce symbolic constants and refer to height consistently. | Stein Somers | -41/+49 | |
| 2020-03-20 | Update test commentary for shared root removal | Mark Rousskov | -9/+2 | |
| 2020-03-06 | Fix & test leak of some BTreeMap nodes on panic during `into_iter` | Stein Somers | -1/+25 | |
| 2020-02-26 | Auto merge of #67290 - jonas-schievink:leak-audit, r=KodrAus | bors | -0/+28 | |
| Audit liballoc for leaks in `Drop` impls when user destructor panics Inspired by https://github.com/rust-lang/rust/pull/67243 and https://github.com/rust-lang/rust/pull/67235, this audits and hopefully fixes the remaining `Drop` impls in liballoc for resource leaks in the presence of panics in destructors called by the affected `Drop` impl. This does not touch `Hash{Map,Set}` since they live in hashbrown. They have similar issues though. r? @KodrAus | ||||
| 2020-02-16 | Lighten tests, in particular for Miri, yet test and explain more | Stein Somers | -20/+32 | |
| 2020-02-04 | Fix and test implementation of BTreeMap's first_entry, last_entry, ↵ | Stein Somers | -11/+21 | |
| pop_first, pop_last | ||||
| 2020-01-30 | Rollup merge of #66648 - crgl:btree-clone-from, r=Amanieu | Dylan DPC | -0/+20 | |
| Implement clone_from for BTreeMap and BTreeSet See #28481. This results in up to 90% speedups on simple data types when `self` and `other` are the same size, and is generally comparable or faster. Some concerns: 1. This implementation requires an `Ord` bound on the `Clone` implementation for `BTreeMap` and `BTreeSet`. Since these structs can only be created externally for keys with `Ord` implemented, this should be fine? If not, there's certainly a less safe way to do this. 2. Changing `next_unchecked` on `RangeMut` to return mutable key references allows for replacing the entire overlapping portion of both maps without changing the external interface in any way. However, if `clone_from` fails it can leave the `BTreeMap` in an invalid state, which might be unacceptable. ~This probably needs an FCP since it changes a trait bound, but (as far as I know?) that change cannot break any external code.~ | ||||
| 2020-01-28 | Include empty BTreeMap in clone_from tests | Charles Gleason | -2/+2 | |
| 2020-01-19 | Fix leak in btree_map::IntoIter when drop panics | Jonas Schievink | -0/+28 | |
| 2019-12-31 | More thorough testing of BTreeMap::range | Stein Somers | -31/+150 | |
| 2019-12-26 | prune ill-conceived BTreeMap iter_mut assertion and test more | Stein Somers | -1/+122 | |
| 2019-12-23 | Add test for BTreeMap::clone_from | Charles Gleason | -0/+20 | |
| 2019-12-22 | Format the world | Mark Rousskov | -55/+53 | |
| 2019-11-29 | Format liballoc with rustfmt | David Tolnay | -6/+1 | |
| 2019-10-23 | proposal for access to BTreeMap/BTreeSet first/last, #62924 | Stein Somers | -0/+73 | |
| 2019-10-18 | BTreeSet symmetric_difference & union optimized, cleaned | Stein Somers | -1/+25 | |
| 2019-10-01 | BTreeSet intersection, difference & is_subnet optimizations | Stein Somers | -18/+92 | |
| 2019-09-16 | Improve BTreeSet::Intersection::size_hint | pcpthm | -0/+11 | |
| The commented invariant that an iterator is smaller than other iterator was violated after next is called and two iterators are consumed at different rates. | ||||
| 2019-08-09 | Rollup merge of #63407 - RalfJung:miri-test-sizes, r=Centril | Mazdak Farrokhzad | -0/+27 | |
| reduce some test sizes in Miri | ||||
| 2019-08-09 | reduce some test sizes in Miri | Ralf Jung | -0/+27 | |
| 2019-08-09 | Merge pull request #1 from rust-lang/master | Sayan Nandan | -5/+61 | |
| Merge recent changes into master | ||||
| 2019-08-09 | Improve tests for liballoc/btree/set | Sayan Nandan | -2/+2 | |
| 2019-05-17 | Use iter() for iterating arrays by slice | Josh Stone | -2/+2 | |
| These `into_iter()` calls will change from iterating references to values if we ever get `IntoIterator` for arrays, which may break the code using that iterator. Calling `iter()` is future proof. | ||||
| 2019-03-29 | improve worst-case performance of BTreeSet difference and intersection | Stein Somers | -0/+61 | |
| 2019-03-10 | we can now skip should_panic tests with the libtest harness | Ralf Jung | -5/+0 | |
| 2019-02-13 | miri: test with slightly larger BTrees | Ralf Jung | -8/+10 | |
| 2019-02-13 | review failures in btree, string | Ralf Jung | -2/+28 | |
| 2019-02-09 | Rollup merge of #58275 - RalfJung:miri-test-libcore, r=Mark-Simulacrum | Mazdak Farrokhzad | -0/+2 | |
| libcore, liballoc: disable tests in Miri I am going to run the libcore and liballoc unit test suites in Miri. Not all tests pass. This PR disables a whole bunch of tests when running in Miri, to get us to a baseline from which I can investigate failures. Cc @SimonSapin @alexcrichton | ||||
| 2019-02-07 | disable tests in Miri | Ralf Jung | -0/+2 | |
| 2019-02-03 | liballoc: revert nested imports style changes. | Mazdak Farrokhzad | -10/+8 | |
| 2019-02-02 | liballoc: adjust abolute imports + more import fixes. | Mazdak Farrokhzad | -1/+1 | |
| 2019-02-02 | liballoc: refactor & fix some imports. | Mazdak Farrokhzad | -9/+13 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -30/+0 | |
| 2018-12-04 | Replace usages of `..i + 1` ranges with `..=i`. | Corey Farwell | -2/+2 | |
| 2018-07-25 | Add missing dyn | Tatsuyuki Ishi | -1/+1 | |
| 2018-03-29 | Move alloc::Bound to {core,std}::ops | Simon Sapin | -1/+1 | |
| The stable reexport `std::collections::Bound` is now deprecated. Another deprecated reexport could be added in `alloc`, but that crate is unstable. | ||||
| 2017-09-22 | Add support for `..=` syntax | Alex Burka | -14/+14 | |
| Add ..= to the parser Add ..= to libproc_macro Add ..= to ICH Highlight ..= in rustdoc Update impl Debug for RangeInclusive to ..= Replace `...` to `..=` in range docs Make the dotdoteq warning point to the ... Add warning for ... in expressions Updated more tests to the ..= syntax Updated even more tests to the ..= syntax Updated the inclusive_range entry in unstable book | ||||
| 2017-06-13 | Merge crate `collections` into `alloc` | Murarth | -0/+1060 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |