From: Dale Wijnand Date: Fri, 20 Apr 2018 21:22:41 +0000 (+0100) Subject: manually line wrap warnings at 80 characters X-Git-Tag: archive/raspbian/0.35.0-2+rpi1~3^2^2^2^2^2^2^2~22^2~1^2~52^2~1 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=d3f5fefa5cd1762dc1c6724eb5bb78b934160dd3;p=cargo.git manually line wrap warnings at 80 characters --- diff --git a/src/cargo/util/toml/targets.rs b/src/cargo/util/toml/targets.rs index 7f7e5a203..d3a04fb5c 100644 --- 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 55950f539..187193668 100644 --- 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 ffb2f38b4..4a6de2001 100644 --- 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` ", ),