- 23 8月, 2013 1 次提交
-
-
由 Vadim Chugunov 提交于
-
- 22 8月, 2013 1 次提交
-
-
由 blake2-ppc 提交于
-
- 21 8月, 2013 1 次提交
-
-
由 Florian Zeitz 提交于
-
- 19 8月, 2013 12 次提交
-
-
由 blake2-ppc 提交于
Embed an iterator in the CharSplitIterator struct, and combine that with the former bool `only_ascii`; so use an enum instead.
-
由 Niko Matsakis 提交于
-
由 blake2-ppc 提交于
-
由 blake2-ppc 提交于
-
由 blake2-ppc 提交于
-
由 blake2-ppc 提交于
-
由 blake2-ppc 提交于
-
由 blake2-ppc 提交于
Let CharIterator be a separate type from CharOffsetIterator (so that CharIterator can be cloned, for example). Implement CharOffsetIterator by using the same technique as the method subslice_offset.
-
由 blake2-ppc 提交于
Add a function like raw::slice_bytes, but it doesn't check slice boundaries. For iterator use where we always know the begin, end indices are in range.
-
由 blake2-ppc 提交于
Implement char_range_at_reverse similarly to char_range_at, instead of re-using that method.
-
由 blake2-ppc 提交于
-
由 blake2-ppc 提交于
-
- 16 8月, 2013 2 次提交
-
-
由 Chris Morgan 提交于
-
由 Huon Wilson 提交于
-
- 14 8月, 2013 2 次提交
-
-
由 Huon Wilson 提交于
If they are on the trait then it is extremely annoying to use them as generic parameters to a function, e.g. with the iterator param on the trait itself, if one was to pass an Extendable<int> to a function that filled it either from a Range or a Map<VecIterator>, one needs to write something like: fn foo<E: Extendable<int, Range<int>> + Extendable<int, Map<&'self int, int, VecIterator<int>>> (e: &mut E, ...) { ... } since using a generic, i.e. `foo<E: Extendable<int, I>, I: Iterator<int>>` means that `foo` takes 2 type parameters, and the caller has to specify them (which doesn't work anyway, as they'll mismatch with the iterators used in `foo` itself). This patch changes it to: fn foo<E: Extendable<int>>(e: &mut E, ...) { ... }
-
由 Marvin Löbel 提交于
Added into_owned() method for vectors Added DoubleEnded Iterator impl to Option Renamed nil.rs to unit.rs
-
- 13 8月, 2013 3 次提交
-
-
由 Alex Crichton 提交于
Closes #5495
-
由 Alex Crichton 提交于
Closes #1651
-
由 Daniel Micay 提交于
-
- 11 8月, 2013 2 次提交
-
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
before: test bench_with_capacity ... bench: 104 ns/iter (+/- 4) after: test bench_with_capacity ... bench: 56 ns/iter (+/- 1)
-
- 10 8月, 2013 6 次提交
-
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
cc #5898
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
- 09 8月, 2013 1 次提交
-
-
由 OGINO Masanori 提交于
Basically, generic containers should not use the default methods since a type of elements may not guarantees total order. str could use them since u8's Ord guarantees total order. Floating point numbers are also broken with the default methods because of NaN. Thanks for @thestinger. Timespec also guarantees total order AIUI. I'm unsure whether extra::semver::Identifier does so I left it alone. Proof needed. Signed-off-by: NOGINO Masanori <masanori.ogino@gmail.com>
-
- 08 8月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
This is everywhere except struct fields and enum variants.
-
- 07 8月, 2013 3 次提交
-
-
由 Erick Tryzelaar 提交于
-
由 Huon Wilson 提交于
Closes #3682.
-
由 Erick Tryzelaar 提交于
-
- 06 8月, 2013 1 次提交
-
-
由 Marvin Löbel 提交于
- Made naming schemes consistent between Option, Result and Either - Changed Options Add implementation to work like the maybe monad (return None if any of the inputs is None) - Removed duplicate Option::get and renamed all related functions to use the term `unwrap` instead
-
- 05 8月, 2013 4 次提交
-
-
由 blake2-ppc 提交于
fn slice_bytes is marked unsafe since it allows violating the valid string encoding property; but the function did also allow extending the lifetime of the slice by mistake, since it's returning `&str`. Use the annotation `slice_bytes<'a>(&'a str, ...) -> &'a str` so that all uses of slice_bytes are region checked correctly.
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-