fix(future): Lead with non-capital letter

Per rustc dev guide

Author: epage

src/cargo/core/compiler/future_incompat.rs

@@ -434,7 +434,7 @@ pub fn save_and_display_report(
     let update_message = if !updated_versions.is_empty() {
         format!(
             "\
-Update to a newer version to see if the issue has been fixed:
+update to a newer version to see if the issue has been fixed
 {updated_versions}",
             updated_versions = updated_versions
         )
@@ -448,8 +448,8 @@ Update to a newer version to see if the issue has been fixed:
             let manifest = bcx.packages.get_one(*package_id).unwrap().manifest();
             format!(
                 "  - {package_spec}
-  - Repository: {url}
-  - Detailed warning command: `cargo report future-incompatibilities --id {id} --package {package_spec}`",
+  - repository: {url}
+  - detailed warning command: `cargo report future-incompatibilities --id {id} --package {package_spec}`",
                 package_spec = format!("{}@{}", package_id.name(), package_id.version()),
                 url = manifest
                     .metadata()
@@ -466,22 +466,22 @@ Update to a newer version to see if the issue has been fixed:
         .iter()
         .all(|report| report.is_local);
 
-    let suggestion_header = "To solve this problem, you can try the following approaches:";
+    let suggestion_header = "to solve this problem, you can try the following approaches:";
     let mut suggestions = Vec::new();
     if !all_is_local {
         if !update_message.is_empty() {
             suggestions.push(update_message);
         }
         suggestions.push(format!(
             "\
-Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
 {upstream_info}"
         ));
         suggestions.push(
             "\
-Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section"
                 .to_owned(),

tests/testsuite/future_incompat_report.rs

@@ -146,16 +146,16 @@ fn incompat_in_dependency() {
         .with_stderr_data(str![[r#"
 [FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
 [WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
-[NOTE] To solve this problem, you can try the following approaches:
+[NOTE] to solve this problem, you can try the following approaches:
 
-- Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+- ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
   - bar@1.0.0
-  - Repository: https://example.com/
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
+  - repository: https://example.com/
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
 
-- Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+- use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
 
@@ -176,16 +176,16 @@ to be in wide use.
 Each warning should contain a link for more information on what the warning
 means and how to resolve it.
 
-To solve this problem, you can try the following approaches:
+to solve this problem, you can try the following approaches:
 
-- Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+- ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
   - bar@1.0.0
-  - Repository: https://example.com/
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
+  - repository: https://example.com/
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
 
-- Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+- use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
 
@@ -595,29 +595,29 @@ fn suggestions_for_updates() {
 [CHECKING] foo v0.1.0 ([ROOT]/foo)
 [FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
 [WARNING] the following packages contain code that will be rejected by a future version of Rust: big_update v1.0.0, with_updates v1.0.0, without_updates v1.0.0
-[NOTE] To solve this problem, you can try the following approaches:
+[NOTE] to solve this problem, you can try the following approaches:
 
-- Update to a newer version to see if the issue has been fixed:
+- update to a newer version to see if the issue has been fixed
 
   - big_update v1.0.0 has the following newer versions available: 2.0.0
   - with_updates v1.0.0 has the following newer versions available: 1.0.1, 1.0.2, 3.0.1
 
-- Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+- ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
   - big_update@1.0.0
-  - Repository: <not found>
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package big_update@1.0.0`
+  - repository: <not found>
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package big_update@1.0.0`
 
   - with_updates@1.0.0
-  - Repository: <not found>
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package with_updates@1.0.0`
+  - repository: <not found>
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package with_updates@1.0.0`
 
   - without_updates@1.0.0
-  - Repository: <not found>
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package without_updates@1.0.0`
+  - repository: <not found>
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package without_updates@1.0.0`
 
-- Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+- use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
 
@@ -638,29 +638,29 @@ to be in wide use.
 Each warning should contain a link for more information on what the warning
 means and how to resolve it.
 
-To solve this problem, you can try the following approaches:
+to solve this problem, you can try the following approaches:
 
-- Update to a newer version to see if the issue has been fixed:
+- update to a newer version to see if the issue has been fixed
 
   - big_update v1.0.0 has the following newer versions available: 2.0.0
   - with_updates v1.0.0 has the following newer versions available: 1.0.1, 1.0.2, 3.0.1
 
-- Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+- ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
   - big_update@1.0.0
-  - Repository: <not found>
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package big_update@1.0.0`
+  - repository: <not found>
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package big_update@1.0.0`
 
   - with_updates@1.0.0
-  - Repository: <not found>
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package with_updates@1.0.0`
+  - repository: <not found>
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package with_updates@1.0.0`
 
   - without_updates@1.0.0
-  - Repository: <not found>
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package without_updates@1.0.0`
+  - repository: <not found>
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package without_updates@1.0.0`
 
-- Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+- use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
 
@@ -700,16 +700,16 @@ fn correct_report_id_when_cached() {
 [CHECKING] foo v1.0.0 ([ROOT]/foo)
 [FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
 [WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
-[NOTE] To solve this problem, you can try the following approaches:
+[NOTE] to solve this problem, you can try the following approaches:
 
-- Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+- ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
   - bar@1.0.0
-  - Repository: https://example.com/
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
+  - repository: https://example.com/
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
 
-- Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+- use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
 
@@ -723,16 +723,16 @@ https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch
         .with_stderr_data(str![[r#"
 [FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
 [WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
-[NOTE] To solve this problem, you can try the following approaches:
+[NOTE] to solve this problem, you can try the following approaches:
 
-- Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
-or even helping with a fix (e.g. by creating a pull request):
+- ensure the maintainers know of this problem (e.g. creating a bug report if needed)
+or even helping with a fix (e.g. by creating a pull request)
 
   - bar@1.0.0
-  - Repository: https://example.com/
-  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
+  - repository: https://example.com/
+  - detailed warning command: `cargo report future-incompatibilities --id 1 --package bar@1.0.0`
 
-- Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
+- use your own version of the dependency with the `[patch]` section in `Cargo.toml`
 For more information, see:
 https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section