diff options
| author | Josh Stone <jistone@redhat.com> | 2019-04-29 18:32:05 -0700 |
|---|---|---|
| committer | Josh Stone <jistone@redhat.com> | 2019-04-29 18:32:05 -0700 |
| commit | 9b3583375dbd45b19b8ce8822b89ff79529354d6 (patch) | |
| tree | 137494b5e5c41e94a3e33f9fe09bada8cb07541c /src/liballoc/string.rs | |
| parent | 00859e3e653973120006aaf3227823062dde1ba7 (diff) | |
| download | rust-9b3583375dbd45b19b8ce8822b89ff79529354d6.tar.gz rust-9b3583375dbd45b19b8ce8822b89ff79529354d6.zip | |
Document the order of {Vec,VecDeque,String}::retain
It's natural for `retain` to work in order from beginning to end, but this wasn't actually documented to be the case. If we actually promise this, then the caller can do useful things like track the index of each element being tested, as [discussed in the forum][1]. This is now documented for `Vec`, `VecDeque`, and `String`. [1]: https://users.rust-lang.org/t/vec-retain-by-index/27697 `HashMap` and `HashSet` also have `retain`, and the `hashbrown` implementation does happen to use a plain `iter()` order too, but it's not certain that this should always be the case for these types.
Diffstat (limited to 'src/liballoc/string.rs')
| -rw-r--r-- | src/liballoc/string.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/liballoc/string.rs b/src/liballoc/string.rs index a3e2098695f..aaa38142693 100644 --- a/src/liballoc/string.rs +++ b/src/liballoc/string.rs @@ -1200,8 +1200,8 @@ impl String { /// Retains only the characters specified by the predicate. /// /// In other words, remove all characters `c` such that `f(c)` returns `false`. - /// This method operates in place and preserves the order of the retained - /// characters. + /// This method operates in place, visiting each character exactly once in the + /// original order, and preserves the order of the retained characters. /// /// # Examples /// |