Skip to content

Commit e4d9d6e

Browse files
add rewording suggested by Wesley
Co-authored-by: Wesley Wiser <wwiser@gmail.com>
1 parent 8075b0f commit e4d9d6e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

posts/inside-rust/2022-09-14-const-eval-safety-rule-revision.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ explicitly catch. We anticipated this: RFC 3016, "const UB", explicitly
182182
Having said that: So much of Rust's success has been built around the trust that
183183
we have earned with our community. Yes, the project has always reserved the
184184
right to make breaking changes when resolving soundness bugs; but we have also
185-
strived to avoid such breakage *whenever feasible*, via things like
185+
strived to mitigate such breakage *whenever feasible*, via things like
186186
[future-incompatible lints][future-incompat].
187187

188188
[future-incompat]: https://doc.rust-lang.org/rustc/lints/index.html#future-incompatible-lints

0 commit comments

Comments
 (0)