Update ui output to latest nightly

This commit is contained in:
Oliver Schneider 2017-11-29 15:45:12 +01:00
parent 34da5d93ef
commit ad63e4eaef
No known key found for this signature in database
GPG Key ID: A69F8D225B3AD7D9
4 changed files with 13 additions and 13 deletions

View File

@ -38,7 +38,7 @@ note: potential failure(s)
|
31 | panic!();
| ^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: consider implementing `TryFrom` instead
--> $DIR/fallible_impl_from.rs:37:1
@ -65,7 +65,7 @@ note: potential failure(s)
| ^^^^^^^^^^^^^^^^^^^^^^^^^
43 | panic!("{:?}", s);
| ^^^^^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: consider implementing `TryFrom` instead
--> $DIR/fallible_impl_from.rs:55:1
@ -87,5 +87,5 @@ note: potential failure(s)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
58 | panic!("{:?}", s);
| ^^^^^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

View File

@ -264,7 +264,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
238 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: Err(_) will match all errors, maybe not a good idea
--> $DIR/matches.rs:246:9
@ -290,7 +290,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
244 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: Err(_) will match all errors, maybe not a good idea
--> $DIR/matches.rs:252:9
@ -316,7 +316,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
250 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: this `match` has identical arm bodies
--> $DIR/matches.rs:258:18
@ -334,7 +334,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
257 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: this `match` has identical arm bodies
--> $DIR/matches.rs:265:18
@ -352,7 +352,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
264 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: this `match` has identical arm bodies
--> $DIR/matches.rs:271:18
@ -370,7 +370,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
270 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: this `match` has identical arm bodies
--> $DIR/matches.rs:277:18
@ -388,5 +388,5 @@ note: consider refactoring into `Ok(3) | Ok(_)`
|
276 | Ok(3) => println!("ok"),
| ^^^^^^^^^^^^^^
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

View File

@ -112,7 +112,7 @@ error: trivial regex
error: trivial regex
--> $DIR/regex.rs:62:40
|
62 | let trivial_backslash = Regex::new("a/.b");
62 | let trivial_backslash = Regex::new("a//.b");
| ^^^^^^^
|
= help: consider using consider using `str::contains`

View File

@ -5,7 +5,7 @@ error: handle written amount returned or use `Write::write_all` instead
| ^^^^^^^^^^^^^^^^^^^^^^^
|
= note: `-D unused-io-amount` implied by `-D warnings`
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: handle read amount returned or use `Read::read_exact` instead
--> $DIR/unused_io_amount.rs:13:5
@ -13,7 +13,7 @@ error: handle read amount returned or use `Read::read_exact` instead
13 | try!(s.read(&mut buf));
| ^^^^^^^^^^^^^^^^^^^^^^^
|
= note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: handle written amount returned or use `Write::write_all` instead
--> $DIR/unused_io_amount.rs:18:5