manually line wrap warnings at 80 characters

diff --git a/src/cargo/util/toml/targets.rs b/src/cargo/util/toml/targets.rs
index 7f7e5a203a51c0cb5a1af844de79b84620c9221f..d3a04fb5c76912ee49ae40564977cbf77d242cb0 100644 (file)
--- a/src/cargo/util/toml/targets.rs
+++ b/src/cargo/util/toml/targets.rs
@@ -595,18 +595,20 @@ fn toml_targets_and_inferred(
                             }
                             warnings.push(format!(
                                 "\
-An explicit [[{section}]] section is specified in Cargo.toml which currently disables Cargo from \
-automatically inferring other {target_kind_human} targets. This inference behavior will change in \
-the Rust 2018 edition and the following files will be included as a {target_kind_human} target:
+An explicit [[{section}]] section is specified in Cargo.toml which currently
+disables Cargo from automatically inferring other {target_kind_human} targets.
+This inference behavior will change in the Rust 2018 edition and the following
+files will be included as a {target_kind_human} target:
 
 {rem_targets_str}
-This is likely to break cargo build or cargo test as these files may not be ready to be compiled \
-as a {target_kind_human} target today. You can future-proof yourself and disable this warning by \
-adding {autodiscover_flag_name} = false to your [package] section. You may also move the files to \
-a location where Cargo would not automatically infer them to be a target, such as in subfolders.
-
-For more information on this warning you can consult https://github.com/rust-lang/cargo/issues/5330\
-                            ",
+This is likely to break cargo build or cargo test as these files may not be
+ready to be compiled as a {target_kind_human} target today. You can future-proof yourself
+and disable this warning by adding {autodiscover_flag_name} = false to your [package]
+section. You may also move the files to a location where Cargo would not
+automatically infer them to be a target, such as in subfolders.
+
+For more information on this warning you can consult
+https://github.com/rust-lang/cargo/issues/5330",
                                 section = target_kind,
                                 target_kind_human = target_kind_human,
                                 rem_targets_str = rem_targets_str,

diff --git a/tests/testsuite/bench.rs b/tests/testsuite/bench.rs
index 55950f539fc4ae85e120b5590f2e6672a13f4cad..1871936684ade275da5f8a2379ef16877f98d8e1 100644 (file)
--- a/tests/testsuite/bench.rs
+++ b/tests/testsuite/bench.rs
@@ -753,18 +753,21 @@ fn bench_autodiscover_2015() {
             .masquerade_as_nightly_cargo(),
         execs().with_stderr(&format!(
             "warning: \
-An explicit [[bench]] section is specified in Cargo.toml which currently disables Cargo from \
-automatically inferring other benchmark targets. This inference behavior will change in \
-the Rust 2018 edition and the following files will be included as a benchmark target:
+An explicit [[bench]] section is specified in Cargo.toml which currently
+disables Cargo from automatically inferring other benchmark targets.
+This inference behavior will change in the Rust 2018 edition and the following
+files will be included as a benchmark target:
 
 * [..]bench_basic.rs
 
-This is likely to break cargo build or cargo test as these files may not be ready to be compiled \
-as a benchmark target today. You can future-proof yourself and disable this warning by \
-adding autobenches = false to your [package] section. You may also move the files to \
-a location where Cargo would not automatically infer them to be a target, such as in subfolders.
+This is likely to break cargo build or cargo test as these files may not be
+ready to be compiled as a benchmark target today. You can future-proof yourself
+and disable this warning by adding autobenches = false to your [package]
+section. You may also move the files to a location where Cargo would not
+automatically infer them to be a target, such as in subfolders.
 
-For more information on this warning you can consult https://github.com/rust-lang/cargo/issues/5330
+For more information on this warning you can consult
+https://github.com/rust-lang/cargo/issues/5330
 [COMPILING] foo v0.0.1 ({})
 [FINISHED] release [optimized] target(s) in [..]
 [RUNNING] target[/]release[/]deps[/]foo-[..][EXE]

diff --git a/tests/testsuite/run.rs b/tests/testsuite/run.rs
index ffb2f38b461887147e058a59090e2ed9a2426458..4a6de2001b43ae0554633b6029ec29fe3827431e 100644 (file)
--- a/tests/testsuite/run.rs
+++ b/tests/testsuite/run.rs
@@ -446,18 +446,21 @@ fn run_example_autodiscover_2015() {
             .masquerade_as_nightly_cargo(),
         execs().with_status(101).with_stderr(
             "warning: \
-An explicit [[example]] section is specified in Cargo.toml which currently disables Cargo from \
-automatically inferring other example targets. This inference behavior will change in \
-the Rust 2018 edition and the following files will be included as a example target:
+An explicit [[example]] section is specified in Cargo.toml which currently
+disables Cargo from automatically inferring other example targets.
+This inference behavior will change in the Rust 2018 edition and the following
+files will be included as a example target:
 
 * [..]a.rs
 
-This is likely to break cargo build or cargo test as these files may not be ready to be compiled \
-as a example target today. You can future-proof yourself and disable this warning by \
-adding autoexamples = false to your [package] section. You may also move the files to \
-a location where Cargo would not automatically infer them to be a target, such as in subfolders.
+This is likely to break cargo build or cargo test as these files may not be
+ready to be compiled as a example target today. You can future-proof yourself
+and disable this warning by adding autoexamples = false to your [package]
+section. You may also move the files to a location where Cargo would not
+automatically infer them to be a target, such as in subfolders.
 
-For more information on this warning you can consult https://github.com/rust-lang/cargo/issues/5330
+For more information on this warning you can consult
+https://github.com/rust-lang/cargo/issues/5330
 error: no example target named `a`
 ",
         ),