-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Improving std::env docs #42091
Improving std::env docs #42091
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (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. |
@@ -13,6 +13,13 @@ | |||
//! This module contains functions to inspect various aspects such as | |||
//! environment variables, process arguments, the current directory, and various | |||
//! other important directories. | |||
//! | |||
//! There are several functions and structs in this module that have a |
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.
I am not convinced this is the best way to describe this. Does this read alright for you?
|
src/libstd/env.rs
Outdated
/// | ||
/// Returns an [`Err`][err] (containing an error message) if one of the input | ||
/// Returns an [`Err`] (containing an error message) if one of the input |
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.
Markdown treats this as a link because it's following parens
You'll need to do something like:
Returns an [`Err`][`Err`] (containing...
or just
Returns an [`Err`][] (containing...
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.
Ah of course! Thank you.
☔ The latest upstream changes (presumably #42105) made this pull request unmergeable. Please resolve the merge conflicts. |
@steveklabnik All seems to be good now. Were there any changes you were wanting? |
Could you squash your commits? Otherwise looks good to me, but @steveklabnik or someone else from doc team should review. |
@Mark-Simulacrum What would be the best way to do this since I needed to do a merge to align to master. Just gave it a shot and have really messed up the history as it rebased the 100 or so commits in between mine on top of mine 😞 |
Looks good to me, thanks for your contribution! @bors r+ rollup |
📌 Commit 55d75c4 has been approved by |
Ah, no worries about the squashing -- I think http://stackoverflow.com/questions/15727597/git-how-to-rebase-and-squash-commits-from-branch-to-master might help if you're interested, but it's not really all that big a problem. |
err... I did not want to close this. |
@frewsxcv Not sure if bors need to be reminded again with the accidental close 😄 |
should be fine, the PR is still in the queue |
Ah I did not know that existed. Great thanks! |
⌛ Testing commit 55d75c4 with merge 6ee90e3... |
💔 Test failed - status-travis |
Any ideas on that one? |
@bors retry
|
Improving std::env docs Addresses rust-lang#29351. Hopefully this addresses the following points: > - iterators should use the standard iterator boilerplate like https://doc.rust-lang.org/std/iter/struct.Map.html, this applies to all structs except for JoinPathsError > - JoinPathsError should properly link the function it comes from and use language similar to https://doc.rust-lang.org/std/io/struct.Error.html > - same wording issues with VarError > - functions need to ensure linkage to things they refer to in their descriptions > - Explain the difference between `os` and non-`os` structs and methods
Addresses #29351.
Hopefully this addresses the following points: