std: fix doctest and explain for as_slices and as_mut_slices in VecDeque

2025-05-21T14:13:23+00:00

Signed-off-by: xizheyin

Implement `VecDeque::truncate_front()`

2025-05-05T15:13:26+00:00

Tracking issue: #140667 Signed-off-by: Vladimir Krivopalov

Fully test the alloc crate through alloctests

2025-03-07T19:11:13+00:00

For the tests that make use of internal implementation details, we include the module to test using #[path] in alloctests now.

[Clippy] Add vec_reserve & vecdeque_reserve diagnostic items

2025-01-25T22:18:18+00:00

Implement `VecDeque::pop_front_if` & `VecDeque::pop_back_if`

2025-01-22T17:04:36+00:00

Add clarity to the "greater" of `VecDeque::insert`

2024-12-14T14:25:55+00:00

Replace i32 by char to add clarity

2024-12-14T14:25:55+00:00

In some `Vec` and `VecDeque` examples where elements are i32, examples can seem a bit confusing at first glance if a parameter of the method is an usize.

Fix predicate signatures in retain_mut docs

2024-10-17T00:52:50+00:00

Auto merge of #126557 - GrigorenkoPV:vec_track_caller, r=joboet

2024-10-14T02:33:40+00:00

Add `#[track_caller]` to allocating methods of `Vec` & `VecDeque` Part 4 in a lengthy saga. r? `@joshtriplett` because they were the reviewer the last 3 times. `@bors` rollup=never "[just in case this has perf effects, Vec is hot](https://github.com/rust-lang/rust/pull/79323#issuecomment-731866746)" This was first attempted in #79323 by `@nvzqz.` It got approval from `@joshtriplett,` but rotted with merge conflicts and got closed. Then it got picked up by `@Dylan-DPC-zz` in #83359. A benchmark was run[^perf], the results (after a bit of thinking[^thinking]) were deemed ok[^ok], but there was a typo[^typo] and the PR was made from a wrong remote in the first place[^remote], so #83909 was opened instead. By the time #83909 rolled around, the methods in question had received some optimizations[^optimizations], so another perf run was conducted[^perf2]. The results were ok[^ok2]. There was a suggestion to add regression tests for panic behavior [^tests], but before it could be addressed, the PR fell victim to merge conflicts[^conflicts] and died again[^rip]. 3 years have passed, and (from what I can tell) this has not been tried again, so here I am now, reviving this old effort. Given how much time has passed and the fact that I've also touched `VecDeque` this time, it probably makes sense to `@bors` try `@rust-timer` [^perf]: https://github.com/rust-lang/rust/pull/83359#issuecomment-804450095 [^thinking]: https://github.com/rust-lang/rust/pull/83359#issuecomment-805286704 [^ok]: https://github.com/rust-lang/rust/pull/83359#issuecomment-812739031 [^typo]: https://github.com/rust-lang/rust/pull/83359#issuecomment-812750205 [^remote]: https://github.com/rust-lang/rust/pull/83359#issuecomment-814067119 [^optimizations]: https://github.com/rust-lang/rust/pull/83909#issuecomment-813736593 [^perf2]: https://github.com/rust-lang/rust/pull/83909#issuecomment-813825552 [^ok2]: https://github.com/rust-lang/rust/pull/83909#issuecomment-813831341 [^tests]: https://github.com/rust-lang/rust/pull/83909#issuecomment-825788964 [^conflicts]: https://github.com/rust-lang/rust/pull/83909#issuecomment-851173480 [^rip]: https://github.com/rust-lang/rust/pull/83909#issuecomment-873569771

Reformat using the new identifier sorting from rustfmt

2024-09-22T23:11:29+00:00

rust/library/alloc/src/collections/vec_deque/mod.rs, branch 1.89.0