Clarify MaybeUninit docs #138005
Clarify MaybeUninit docs #138005
Conversation
rustbot
added
S-waiting-on-review
| /// according to the requirements of the variable's type. For example, a variable of | ||
| /// reference type must be aligned and non-null. This is an invariant that must | ||
| /// Every variable must be properly initialized according to the requirements of its type. | ||
| /// For example, a variable of reference type must be aligned and non-null. This is an invariant that must |
There was a problem hiding this comment.
You're still dong changes here without explaining the rhyme or reason for them. What is wrong with the sentence that you changed here, the first sentence of this section?
Sorry, I'm already swamped with reviews, I really don't have the time to tease out the meaningful changes from the gratuitous rewordings in a PR like this.
There was a problem hiding this comment.
The idea here is to remove the distraction of mentioning the compiler. (Since it is really the language definition that matters, not what the compiler assumes...)
There was a problem hiding this comment.
That is the rigorous way of talking about it, but not the most accessible way. We have to be careful not to turn the docs into unreadable (to most of the audience) legalese.
|
r? libs-api |
rustbot
added
the
T-libs-api
|
Please decide how yo want to continue with this: close one of #136689 or this PR, and then for the remaining PR, if you want me to review it I'd like you to explain every single change on a paragraph-by-paragraph basis. If that feels like too much, you're doing too many changes in one PR, so please cut it down -- there can always be a next PR. Smaller PRs are a lot easier to review. |
|
☔ The latest upstream changes (presumably #138714) made this pull request unmergeable. Please resolve the merge conflicts. |
This is an attempt at excluding less impactful changes from #136689.
r? @RalfJung