From f5723e51a19b4605a5a72646424fdefb3c3aee94 Mon Sep 17 00:00:00 2001 From: Andy Russell Date: Fri, 22 Feb 2019 13:56:19 -0500 Subject: [PATCH] convert unused doc comments to regular comments --- src/cargo/core/features.rs | 22 +++++++++++----------- tests/testsuite/resolve.rs | 14 +++++++------- 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/src/cargo/core/features.rs b/src/cargo/core/features.rs index 637c9526b48..4daed85d7ef 100644 --- a/src/cargo/core/features.rs +++ b/src/cargo/core/features.rs @@ -150,17 +150,17 @@ macro_rules! stab { }; } -/// A listing of all features in Cargo -/// -/// "look here" -/// -/// This is the macro that lists all stable and unstable features in Cargo. -/// You'll want to add to this macro whenever you add a feature to Cargo, also -/// following the directions above. -/// -/// Note that all feature names here are valid Rust identifiers, but the `_` -/// character is translated to `-` when specified in the `cargo-features` -/// manifest entry in `Cargo.toml`. +// A listing of all features in Cargo. +// +// "look here" +// +// This is the macro that lists all stable and unstable features in Cargo. +// You'll want to add to this macro whenever you add a feature to Cargo, also +// following the directions above. +// +// Note that all feature names here are valid Rust identifiers, but the `_` +// character is translated to `-` when specified in the `cargo-features` +// manifest entry in `Cargo.toml`. features! { pub struct Features { diff --git a/tests/testsuite/resolve.rs b/tests/testsuite/resolve.rs index f282628f346..3bc6654e051 100644 --- a/tests/testsuite/resolve.rs +++ b/tests/testsuite/resolve.rs @@ -14,13 +14,13 @@ use crate::support::resolver::{ use proptest::{prelude::*, *}; -/// NOTE: proptest is a form of fuzz testing. It generates random input and makes sure that -/// certain universal truths are upheld. Therefore, it can pass when there is a problem, -/// but if it fails then there really is something wrong. When testing something as -/// complicated as the resolver, the problems can be very subtle and hard to generate. -/// We have had a history of these tests only failing on PRs long after a bug is introduced. -/// If you have one of these test fail please report it on #6258, -/// and if you did not change the resolver then feel free to retry without concern. +// NOTE: proptest is a form of fuzz testing. It generates random input and makes sure that +// certain universal truths are upheld. Therefore, it can pass when there is a problem, +// but if it fails then there really is something wrong. When testing something as +// complicated as the resolver, the problems can be very subtle and hard to generate. +// We have had a history of these tests only failing on PRs long after a bug is introduced. +// If you have one of these test fail please report it on #6258, +// and if you did not change the resolver then feel free to retry without concern. proptest! { #![proptest_config(ProptestConfig { max_shrink_iters: