-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Various tutorial fixes. #10880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various tutorial fixes. #10880
Conversation
|
||
# Creating Documentation | ||
|
||
Documenting Rust APIs is quite simple To document a given item, we have "doc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/T/t/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/simple To/simple. To/
cc @thestinger for the tutorial parts. |
Objects are never accessible after their destructor has been called, so there | ||
are no dynamic failures from accessing freed resources. When a task fails, the | ||
Destructors are only called once an object is inaccessible, so no dynamic | ||
failures are possible from accessing freed resources. When a task fails, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change does not mean precisely the same thing as the original sentence. In particular, the original phrasing indicates that inaccessibility is a property you get after the destructor has finished. (The new phrasing could be misinterpreted as meaning that the object is inaccessible even from the destructor itself. Of course this is not true, but the potential for such misinterpretation could cause confusion.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The insertion of the word "otherwise" before "inaccessible" would be one way to remedy that concern, but it's heading into the domain of wordiness.
Also no longer reference mutable fields
This is literally a copy-paste, there's no need to have this duplication.
Many of them are small. Will squash on request, but I feel like it's easier for everyone (easier to see and back out individual changes) this way.
Many of them are small. Will squash on request, but I feel like it's easier
for everyone (easier to see and back out individual changes) this way.