rust/src/liballoc/btree/map.rs, branch master

Move some alloc crate top-level items to a new alloc::collections module

2018-06-29T12:01:33+00:00

This matches std::collections

Stabilize entry-or-default

2018-06-10T10:59:12+00:00

Copy changes from HashMap over to BTreeMap.

2018-06-03T00:44:15+00:00

stabilize RangeBounds collections_range #30877

2018-05-24T12:01:40+00:00

rename RangeBounds::start() -> start_bound() rename RangeBounds::end() -> end_bound()

Make an ensure_root_is_owned method to reduce duplication

2018-05-08T17:28:49+00:00

Also remove some unnecessary debug_assert! when creating the shared root, since the root should be stored in the rodata and thus be impossible to accidentally modify.

Add debug asserts and fix some violations

2018-05-08T02:14:34+00:00

Don't drop the shared static node

2018-05-08T02:14:34+00:00

We modify the drop implementation in IntoIter to not drop the shared root

Add a statically allocated empty node for empty maps

2018-05-08T02:14:20+00:00

This gives a pointer to that static empty node instead of allocating a new node, and then whenever inserting makes sure that the root isn't that empty node.

Tweak some stabilizations in libstd

2018-04-19T23:53:12+00:00

This commit tweaks a few stable APIs in the `beta` branch before they hit stable. The `str::is_whitespace` and `str::is_alphanumeric` functions were deleted (added in #49381, issue at #49657). The `and_modify` APIs added in #44734 were altered to take a `FnOnce` closure rather than a `FnMut` closure. Closes #49581 Closes #49657

Auto merge of #48945 - clarcharr:iter_exhaust, r=Kimundi

2018-04-16T13:21:56+00:00

Replace manual iterator exhaust with for_each(drop) This originally added a dedicated method, `Iterator::exhaust`, and has since been replaced with `for_each(drop)`, which is more idiomatic. This is just shorthand for `for _ in &mut self {}` or `while let Some(_) = self.next() {}`. This states the intent a lot more clearly than the identical code: run the iterator to completion. At least personally, my eyes tend to gloss over `for _ in &mut self {}` without fully paying attention to what it does; having a `Drop` implementation akin to: ~~`for _ in &mut self {}; unsafe { free(self.ptr); }`~~ Is not as clear as: `self.exhaust(); unsafe { free(self.ptr); }` ~~Additionally, I've seen debate over whether `while let Some(_) = self.next() {}` or `for _ in &mut self {}` is more clear, whereas `self.exhaust()` is clearer than both.~~