diff options
| author | Aleksey Kladov <aleksey.kladov@gmail.com> | 2019-07-09 19:10:22 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-07-09 19:10:22 +0300 |
| commit | b052fbb54b09f4bf5e428929758671419de87a63 (patch) | |
| tree | 6fad477877152bc78178d4ea137fec613790feea | |
| parent | 8175a1f905d1bf8ffd33c1be48476161d30b885e (diff) | |
| download | rust-b052fbb54b09f4bf5e428929758671419de87a63.tar.gz rust-b052fbb54b09f4bf5e428929758671419de87a63.zip | |
Apply suggestions from code review
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
| -rw-r--r-- | src/libcore/macros.rs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/libcore/macros.rs b/src/libcore/macros.rs index da28afd97c3..2e999a0682b 100644 --- a/src/libcore/macros.rs +++ b/src/libcore/macros.rs @@ -149,7 +149,7 @@ macro_rules! assert_ne { /// `debug_assert!` statements unless `-C debug-assertions` is passed to the /// compiler. This makes `debug_assert!` useful for checks that are too /// expensive to be present in a release build but may be helpful during -/// development. `debug_assert!` statements are always type checked. +/// development. The result of expanding `debug_assert!` is always type checked. /// /// An unchecked assertion allows a program in an inconsistent state to keep /// running, which might have unexpected consequences but does not introduce @@ -194,7 +194,7 @@ macro_rules! debug_assert { /// `debug_assert_eq!` statements unless `-C debug-assertions` is passed to the /// compiler. This makes `debug_assert_eq!` useful for checks that are too /// expensive to be present in a release build but may be helpful during -/// development. `debug_assert_eq!` statements are always type checked. +/// development. The result of expanding `debug_assert_eq!` is always type checked. /// /// [`assert_eq!`]: ../std/macro.assert_eq.html /// @@ -221,7 +221,7 @@ macro_rules! debug_assert_eq { /// `debug_assert_ne!` statements unless `-C debug-assertions` is passed to the /// compiler. This makes `debug_assert_ne!` useful for checks that are too /// expensive to be present in a release build but may be helpful during -/// development. `debug_assert_ne!` statements are always type checked. +/// development. The result of expanding `debug_assert_ne!` is always type checked. /// /// [`assert_ne!`]: ../std/macro.assert_ne.html /// |