Skip to content

Commit cf7195d

Browse files
fix wording
Co-authored-by: Jacob Lifshay <[email protected]>
1 parent 705cd9a commit cf7195d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/3559-rust-has-provenance.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ LLVM has been stuck in this limbo (various proposals but no consensus on how to
239239
If LLVM ends up accepting either of these proposals, it will be entirely compatible with this RFC.
240240
If LLVM makes some different choice, that might be incompatible with Rust's choices.
241241
However, it's not possible to specify Rust in a way that is compatible with "whatever LLVM will do".
242-
There has been no progress on these questions on the side of the LLVM project for many years (as far as the author is aware), and no concrete proposal aside from the one sketched above, so there are only two options: (a) wait until LLVM does something, and then do something compatible in Rust, or (b) do something that makes sense for Rust, and if eventually there is movement on the LLVM side, work with them to ensure Rust's needs are covered.
242+
There has been no progress on these questions on the side of the LLVM project for many years (as far as the author is aware), and no concrete proposals aside from the ones sketched above, so there are only two options: (a) wait until LLVM does something, and then do something compatible in Rust, or (b) do something that makes sense for Rust, and if eventually there is movement on the LLVM side, work with them to ensure Rust's needs are covered.
243243
(a) means indefinitely blocking progress on pressing questions in the Rust semantics, so this RFC takes the position that we should do (b).
244244
(To the author's knowledge, GCC is not in a better position, and it suffers from [similar bugs](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82282), so we can't use their semantics for guidance either.)
245245

0 commit comments

Comments
 (0)