- 14 12月, 2021 1 次提交
-
-
由 Frank Steffahn 提交于
-
- 01 11月, 2021 4 次提交
-
-
由 Thom Chiovoloni 提交于
-
由 Thom Chiovoloni 提交于
-
由 Thom Chiovoloni 提交于
Co-authored-by: Nthe8472 <the8472@users.noreply.github.com>
-
由 Thom Chiovoloni 提交于
-
- 31 10月, 2021 1 次提交
-
-
由 John Kugelman 提交于
-
- 22 10月, 2021 1 次提交
-
-
由 Caleb Sander 提交于
This addresses a TODO comment. The behavior of #[derive(Clone)] *does* result in a T: Clone requirement. Add a manual Clone implementation, matching Split and SplitInclusive.
-
- 12 10月, 2021 2 次提交
-
-
由 Martin von Zweigbergk 提交于
`[].split_inclusive()` currently yields a single, empty slice. That's different from `"".split_inslusive()`, which yields no output at all. I think that makes the slice version harder to use. The case where I ran into this bug was when writing code for generating a diff between two slices of bytes. I wanted to prefix removed lines with "-" and a added lines with "+". Due to `split_inclusive()`'s current behavior, that means that my code prints just a "-" or "+" for empty files. I suspect most existing callers have similar "bugs" (which would be fixed by this patch). Closes #89716.
-
由 John Kugelman 提交于
-
- 11 10月, 2021 1 次提交
-
-
由 John Kugelman 提交于
-
- 12 8月, 2021 1 次提交
-
-
由 Frank Steffahn 提交于
Adds extensive test for all the [r]split* iterators. Fixes size_hint upper bound for split_inclusive* iterators which was one higher than necessary for non-empty slices. Fixes size_hint lower bound for [r]splitn* iterators when n==0, which was one too high.
-
- 28 7月, 2021 1 次提交
-
-
由 Frank Steffahn 提交于
Add TrustedRandomAccessNoCoerce supertrait without requirements or guarantees about subtype coercions Update all the TrustedRandomAccess impls to also implement the new supertrait
-
- 26 7月, 2021 1 次提交
-
-
由 ibraheemdev 提交于
-
- 03 7月, 2021 1 次提交
-
-
由 The8472 提交于
-
- 17 6月, 2021 1 次提交
-
-
由 Jacob Hoffman-Andrews 提交于
This method on the Iterator trait is doc(hidden), and about half of implementations were doc(hidden). This adds the attribute to the remaining implementations.
-
- 22 3月, 2021 1 次提交
-
-
由 Mara Bos 提交于
-
- 05 3月, 2021 1 次提交
-
-
由 Emilio Cobos Álvarez 提交于
Much like #72584. As per #58957 there's no blocker for this, and I wanted to use this today :-)
-
- 27 2月, 2021 1 次提交
-
-
由 Waffle 提交于
This commit adds `as_str` methods to `SplitWhitespace` and `SplitAsciiWhitespace` str iterators. The methods return the remainder, similar to `as_str` methods on `Chars` and other split iterators. This commit also makes fields of some iterators `pub(crate)`.
-
- 26 2月, 2021 1 次提交
-
-
由 Joshua Nelson 提交于
Note that float methods in `core::intrinsics` weren't converted because they are only defined in `std` (using language item hacks).
-
- 16 2月, 2021 1 次提交
-
-
由 Tomasz Miąsko 提交于
The `may_have_side_effect` is an implementation detail of `TrustedRandomAccess` trait. It describes if obtaining an iterator element may have side effects. It is currently implemented as an associated function. Turn `may_have_side_effect` into an associated constant. This makes the value immediately available to the optimizer.
-
- 13 1月, 2021 1 次提交
-
-
由 Ashley Mannix 提交于
-
- 08 1月, 2021 2 次提交
-
-
由 Marcus Svensson 提交于
-
由 Marcus Svensson 提交于
-
- 05 1月, 2021 1 次提交
-
-
由 Ian Jackson 提交于
Closes #72360. Signed-off-by: NIan Jackson <ijackson@chiark.greenend.org.uk>
-
- 31 12月, 2020 1 次提交
-
-
由 Clément Renault 提交于
-
- 11 12月, 2020 3 次提交
-
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
- 10 12月, 2020 6 次提交
-
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
由 Clément Renault 提交于
-
- 06 10月, 2020 1 次提交
-
-
由 AnthonyMikh 提交于
-
- 05 10月, 2020 1 次提交
-
-
由 Scott McMurray 提交于
Allows getting the slices directly, rather than just through an iterator as in `array_chunks(_mut)`. The constructors for those iterators are then written in terms of these methods, so the iterator constructors no longer have any `unsafe` of their own.
-
- 26 9月, 2020 2 次提交
-
-
由 Guillaume Gomez 提交于
-
由 Matthew Jasper 提交于
It's possible for method resolution to pick this method over a lower priority stable method, causing compilation errors. Since this method is permanently unstable, give it a name that is very unlikely to be used in user code.
-
- 18 9月, 2020 2 次提交