- 06 2月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
-
- 04 2月, 2015 1 次提交
-
-
由 Aaron Turon 提交于
As part of [RFC 474](https://github.com/rust-lang/rfcs/pull/474), this commit renames `std::path` to `std::old_path`, leaving the existing path API in place to ease migration to the new one. Updating should be as simple as adjusting imports, and the prelude still maps to the old path APIs for now. [breaking-change]
-
- 03 2月, 2015 2 次提交
-
-
由 Jorge Aparicio 提交于
Also `for x in option.iter_mut()` -> `if let Some(ref mut x) = option`
-
由 Jorge Aparicio 提交于
-
- 02 2月, 2015 1 次提交
-
-
由 Seo Sanghyeon 提交于
-
- 30 1月, 2015 1 次提交
-
-
由 Tom Jakubowski 提交于
Fix #21442
-
- 29 1月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
-
- 28 1月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 26 1月, 2015 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 22 1月, 2015 3 次提交
-
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Alex Crichton 提交于
-
- 21 1月, 2015 2 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Diggory Blake 提交于
Added doc test
-
- 18 1月, 2015 5 次提交
-
-
由 Seo Sanghyeon 提交于
-
由 Tom Jakubowski 提交于
Fix #21348
-
由 Tom Jakubowski 提交于
This is wanted by external tooling that uses rustdoc. There are likely some bugs when actually generating HTML output (which may expect to be able to read the source) but all I need for now is the cleaned crate and analysis.
-
由 Tom Jakubowski 提交于
-
由 Paul Collier 提交于
-
- 16 1月, 2015 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 13 1月, 2015 3 次提交
-
-
由 Tom Jakubowski 提交于
Fix #20299
-
由 Tom Jakubowski 提交于
-
由 Tom Jakubowski 提交于
Projection predicates on re-exports, for the time being, are rendered as equality predicates because that's easier. It would be nice to fix this in the future. Some gymnastics were needed to remove redundant bounds from the `types` and `lifetimes` fields, remove implicit `Sized` bounds, and re-create `?Sized` bounds. Fix #20203, fix #20924, fix #20911, fix #20534
-
- 09 1月, 2015 1 次提交
-
-
由 Huon Wilson 提交于
-
- 08 1月, 2015 3 次提交
-
-
由 Alex Crichton 提交于
-
由 Tom Jakubowski 提交于
e.g. `Foo<Output=A>` This does not work cross-crate unfortunately. Part of #20646
-
由 Jorge Aparicio 提交于
-
- 07 1月, 2015 3 次提交
-
-
由 Sean McArthur 提交于
fmt::Show is for debugging, and can and should be implemented for all public types. This trait is used with `{:?}` syntax. There still exists #[derive(Show)]. fmt::String is for types that faithfully be represented as a String. Because of this, there is no way to derive fmt::String, all implementations must be purposeful. It is used by the default format syntax, `{}`. This will break most instances of `{}`, since that now requires the type to impl fmt::String. In most cases, replacing `{}` with `{:?}` is the correct fix. Types that were being printed specifically for users should receive a fmt::String implementation to fix this. Part of #20013 [breaking-change]
-
由 Nick Cameron 提交于
-
由 Corey Richardson 提交于
-
- 06 1月, 2015 2 次提交
-
-
由 Jorge Aparicio 提交于
-
由 Jorge Aparicio 提交于
-
- 05 1月, 2015 2 次提交
-
-
由 Huon Wilson 提交于
This implements RFC 179 by making the pattern `&<pat>` require matching against a variable of type `&T`, and introducing the pattern `&mut <pat>` which only works with variables of type `&mut T`. The pattern `&mut x` currently parses as `&(mut x)` i.e. a pattern match through a `&T` or a `&mut T` that binds the variable `x` to have type `T` and to be mutable. This should be rewritten as follows, for example, for &mut x in slice.iter() { becomes for &x in slice.iter() { let mut x = x; Due to this, this is a [breaking-change] Closes #20496.
-
由 Huon Wilson 提交于
Imports may need to be updated so this is a [breaking-change]
-
- 04 1月, 2015 3 次提交
-
-
由 Brendan Zabarauskas 提交于
-
由 Jorge Aparicio 提交于
-
由 Jorge Aparicio 提交于
-
- 01 1月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
-
- 31 12月, 2014 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 30 12月, 2014 1 次提交
-
-
由 Niko Matsakis 提交于
-