diff options
| author | bors <bors@rust-lang.org> | 2019-11-13 03:48:42 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-11-13 03:48:42 +0000 |
| commit | 374ad1b0063963060a00a3110e44d76e7105d059 (patch) | |
| tree | d3822ca1549a4b80df6ee68dbaef92862c8609a8 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 0f12bad718bb8b1fb2b1b7267a02fffaef6e1e3c (diff) | |
| parent | ffeac1f71fe8d8206c9c83747cdd7816ad9aafc2 (diff) | |
| download | rust-374ad1b0063963060a00a3110e44d76e7105d059.tar.gz rust-374ad1b0063963060a00a3110e44d76e7105d059.zip | |
Auto merge of #65637 - ssomers:master, r=scottmcm
proposal for BTreeMap/Set min/max, #62924 - Which pair of names: #62924 lists the existing possibilities min/max, first/last, (EDIT) front/back, peek(/peek_back?). Iterators have next/next_back or next/last. I'm slightly in favour of first/last because min/max might suggest they search over the entire map, and front/back pretends they are only about position. - Return key only instead of pair like iterator does? - If not, then keep the _key_value suffix? ~~Also provide variant with mutable value? But there is no such variant for get_key_value.~~ - Look for and upgrade more usages of `.iter().next()` and such in the libraries? I only upgraded the ones I contributed myself, all very recently.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions