diff options
| author | pierwill <pierwill@users.noreply.github.com> | 2020-06-28 00:06:48 -0700 |
|---|---|---|
| committer | pierwill <pierwill@users.noreply.github.com> | 2020-06-28 00:08:53 -0700 |
| commit | 4595fa8a1baf95b0a19aae3d84e945344d8f8a44 (patch) | |
| tree | 4b2f6ffb051059d2f3598692650c3dbf182994ed | |
| parent | 9bdd2db3a60176012f4dc240eea02d615cc60061 (diff) | |
| download | rust-4595fa8a1baf95b0a19aae3d84e945344d8f8a44.tar.gz rust-4595fa8a1baf95b0a19aae3d84e945344d8f8a44.zip | |
Fix comma in debug_assert! docs
| -rw-r--r-- | src/libcore/macros/mod.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/macros/mod.rs b/src/libcore/macros/mod.rs index 3cfdde60135..5620d26af40 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! /// |