about summary refs log tree commit diff
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2020-07-01 07:43:00 -0700
committerGitHub <noreply@github.com>2020-07-01 07:43:00 -0700
commitaffd950ed2d7a2bff19d984884b98b7eb6885836 (patch)
tree19c90161a7809e271f4961007a2526abf2cee4af
parentdb900d4ef35ac185811d5694b08b86cbc8412bea (diff)
parent4595fa8a1baf95b0a19aae3d84e945344d8f8a44 (diff)
downloadrust-affd950ed2d7a2bff19d984884b98b7eb6885836.tar.gz
rust-affd950ed2d7a2bff19d984884b98b7eb6885836.zip
Rollup merge of #73846 - pierwill:pierwill-patch-2, r=joshtriplett
Fix comma in debug_assert! docs
-rw-r--r--src/libcore/macros/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/macros/mod.rs b/src/libcore/macros/mod.rs
index 13c0e8daf74..17f7349bac2 100644
--- a/src/libcore/macros/mod.rs
+++ b/src/libcore/macros/mod.rs
@@ -151,7 +151,7 @@ macro_rules! assert_ne {
 /// An unchecked assertion allows a program in an inconsistent state to keep
 /// running, which might have unexpected consequences but does not introduce
 /// unsafety as long as this only happens in safe code. The performance cost
-/// of assertions, is however, not measurable in general. Replacing [`assert!`]
+/// of assertions, however, is not measurable in general. Replacing [`assert!`]
 /// with `debug_assert!` is thus only encouraged after thorough profiling, and
 /// more importantly, only in safe code!
 ///