-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Improve the documentation for std::convert (From, Into, AsRef and AsMut) #59330
Improve the documentation for std::convert (From, Into, AsRef and AsMut) #59330
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @shepmaster (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
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.
Some nits on indentations.
Hey hey! I won't have time until tomorrow to review this; @rust-lang/docs can you check it out in the meantime? Thanks so much! |
One of the thing I find that it's hard to review docs PR because we don't have Building whole rust documentation for small changes is overkill and it is so slow |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@lzutao I can provide a tar or zip of the generated docs somehow but that isn't really ideal of course. Maybe it can be added as a downloadable asset at each Travis CI pipeline? I used to do that with Gitlab pipelines, not sure if Travis can do such a thing as well though. |
@ehuss @lzutao @steveklabnik Let me know if there's anything else I can do to improve things! |
This PR needs an review from Documentation team I think. You could ping any of them for requesting review. |
I'm planning on reviewing within the next few hours. |
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.
Hey hey! This PR is great content-wise, I just have some formatting stuff. Please let me know if any of that isn't clear! As soon as the formatting is fixed, we can merge this in 👍
@steveklabnik Thanks for your kind words! I fixed all the issues you brought up, thanks a lot for all the feedback :) Many of the things I was unaware of / didn't know so it will probably help me when I do some editing in the future as well. I was wondering!: Are there are other things I could maybe help with? I am not sure if there are still documents to be reviewed? Or if there is some documentation that needs a test read / that needs some improvement? Now that I got the hang of it a little bit I would enjoy contributing some more! Let me know if there's anything I can do to help :) |
Awesome, thanks! @bors: r+ rollup
For sure! We have a T-docs tag with issues. Picking out one of them and writing some docs would be fantastic! |
📌 Commit 6c479c3 has been approved by |
…ation, r=steveklabnik Improve the documentation for std::convert (From, Into, AsRef and AsMut) # Description In this PR I updated the documentation of From, Into, AsRef and AsMut, as well as the general std::convert module documentation. The discussion in rust-lang#59163 provided information that was not yet present in the docs, or was not expressed clearly enough. I tried to clarify the examples that were already present in the docs as well as add more information about considered best-practices that came out of the discussion in rust-lang#59163 @steveklabnik I hope I didn't change too much. This is an initial version! I will scan through everything tomorrow as well again to see if I made any typo's or errors, and maybe make some small changes here and there. All suggestions are welcome! closes rust-lang#59163
Rollup of 7 pull requests Successful merges: - #59004 ([rustdoc] Improve "in parameters" search and search more generally) - #59026 (Fix moving text in search tabs headers) - #59197 (Exclude old book redirect stubs from search engines) - #59330 (Improve the documentation for std::convert (From, Into, AsRef and AsMut)) - #59424 (Fix code block display in portability element in dark theme) - #59427 (Link to PhantomData in NonNull documentation) - #59432 (Improve some compiletest documentation) Failed merges: r? @ghost
Rollup of 7 pull requests Successful merges: - #59004 ([rustdoc] Improve "in parameters" search and search more generally) - #59026 (Fix moving text in search tabs headers) - #59197 (Exclude old book redirect stubs from search engines) - #59330 (Improve the documentation for std::convert (From, Into, AsRef and AsMut)) - #59424 (Fix code block display in portability element in dark theme) - #59427 (Link to PhantomData in NonNull documentation) - #59432 (Improve some compiletest documentation) Failed merges: r? @ghost
Description
In this PR I updated the documentation of From, Into, AsRef and AsMut, as well as the general std::convert module documentation. The discussion in #59163 provided information that was not yet present in the docs, or was not expressed clearly enough. I tried to clarify the examples that were already present in the docs as well as add more information about considered best-practices that came out of the discussion in #59163
@steveklabnik I hope I didn't change too much. This is an initial version! I will scan through everything tomorrow as well again to see if I made any typo's or errors, and maybe make some small changes here and there.
All suggestions are welcome!
closes #59163