-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Describe VecDeque with more consistent names #93899
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @yaahc (rust-highfive has picked a reviewer for you, use r? to override) |
It might be good to introduce the word - A double-ended queue implemented with a growable ring buffer.
+ A double-ended queue (deque) implemented with a growable ring buffer. |
e375ac3
to
5cdee93
Compare
It is indeed. |
5cdee93
to
5d53597
Compare
Oops, only now I noticed that I did find and replace the word "queue", leading to the unfortunate description "double-ended deque". Fixed. |
@bors r+ rollup |
📌 Commit 5d53597 has been approved by |
…askrgr Rollup of 5 pull requests Successful merges: - rust-lang#93899 (Describe VecDeque with more consistent names) - rust-lang#93949 (Add basic platform support to library/{panic_}unwind for m68k) - rust-lang#93999 (suggest using raw strings when invalid escapes appear in literals) - rust-lang#94001 (llvm: migrate to new parameter-bearing uwtable attr) - rust-lang#94014 (Move transmute_undefined_repr back to nursery) Failed merges: - rust-lang#94020 (Support pretty printing of invalid constants) r? `@ghost` `@rustbot` modify labels: rollup
The public documentation of VecDeque starts describing itself as a "queue". In method descriptions, it's
neversometimes named queue again, orVecDeque
(IMO a sometimes useful and often noisy notation) or "deque" or "vector". In examples,deque
,v
(hidden inrange_mut
) orvector
. Here is a subjective attempt at more consistency.