bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Auto merge of #87445 - amalik18:issue-83584-fix, r=kennytm

Browse source 
Fix may not to appropriate might not or must not

I went through and changed occurrences of `may not` to be more explicit with `might not` and `must not`.
This commit is contained in:
bors 2021-07-30 04:34:13 +00:00
commit fe1c942eee
49 changed files with 96 additions and 96 deletions
Download patch file Download diff file Expand all files Collapse all files

4
library/std/src/panic.rs
View file

@ -163,7 +163,7 @@ pub auto trait RefUnwindSafe {}
/// When using [`catch_unwind`] it may be the case that some of the closed over
/// variables are not unwind safe. For example if `&mut T` is captured the
/// compiler will generate a warning indicating that it is not unwind safe. It
/// may not be the case, however, that this is actually a problem due to the
/// might not be the case, however, that this is actually a problem due to the
/// specific usage of [`catch_unwind`] if unwind safety is specifically taken into
/// account. This wrapper struct is useful for a quick and lightweight
/// annotation that a variable is indeed unwind safe.
@ -406,7 +406,7 @@ impl<S: Stream> Stream for AssertUnwindSafe<S> {
///
/// # Notes
///
/// Note that this function **may not catch all panics** in Rust. A panic in
/// Note that this function **might not catch all panics** in Rust. A panic in
/// Rust is not always implemented via unwinding, but can be implemented by
/// aborting the process as well. This function *only* catches unwinding panics,
/// not those that abort the process.