about summary refs log tree commit diff
path: root/src/libcore
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2020-05-19 13:53:47 +0200
committerGitHub <noreply@github.com>2020-05-19 13:53:47 +0200
commit745ca2afae768b5228bee15eeb37531313a5a435 (patch)
tree66bd44168250f99b548ae126d68a1f3f05c748ea /src/libcore
parent817880842c268ecedc2ce997dbc158f8722ba4e2 (diff)
parent5b65c0f9a5506d154b41048356dfa9807386b0c8 (diff)
downloadrust-745ca2afae768b5228bee15eeb37531313a5a435.tar.gz
rust-745ca2afae768b5228bee15eeb37531313a5a435.zip
Rollup merge of #72344 - kornelski:assertdoc, r=Mark-Simulacrum
Assert doc wording

The current wording implies unsafe code is dependent on assert:

https://users.rust-lang.org/t/are-assert-statements-included-in-unsafe-blocks/42865
Diffstat (limited to 'src/libcore')
-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 14bfa8bab89..13a569e81d0 100644
--- a/src/libcore/macros/mod.rs
+++ b/src/libcore/macros/mod.rs
@@ -1243,7 +1243,7 @@ pub(crate) mod builtin {
     /// be disabled. See [`debug_assert!`] for assertions that are not enabled in
     /// release builds by default.
     ///
-    /// Unsafe code relies on `assert!` to enforce run-time invariants that, if
+    /// Unsafe code may rely on `assert!` to enforce run-time invariants that, if
     /// violated could lead to unsafety.
     ///
     /// Other use-cases of `assert!` include testing and enforcing run-time