Uh oh!
There was an error while loading. Please reload this page.
Improving std::env docs - #42091
Conversation
rust-highfive
commented
May 18, 2017
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. |
maccoda
commented
May 18, 2017
| //! 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.
I am not convinced this is the best way to describe this. Does this read alright for you?
frewsxcv
commented
May 19, 2017
|
| /// # Errors | ||
| /// | ||
| /// 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.
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.
Ah of course! Thank you.
bors
commented
May 19, 2017
☔ The latest upstream changes (presumably #42105) made this pull request unmergeable. Please resolve the merge conflicts. |
maccoda
commented
May 20, 2017
@steveklabnik All seems to be good now. Were there any changes you were wanting? |
Mark-Simulacrum
commented
May 20, 2017
Could you squash your commits? Otherwise looks good to me, but @steveklabnik or someone else from doc team should review. |
maccoda
commented
May 20, 2017
@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 😞 |
frewsxcv
commented
May 20, 2017
Looks good to me, thanks for your contribution! @bors r+ rollup |
bors
commented
May 20, 2017
📌 Commit 55d75c4 has been approved by |
Mark-Simulacrum
commented
May 20, 2017
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. |
Mark-Simulacrum
commented
May 20, 2017
err... I did not want to close this. |
maccoda
commented
May 20, 2017
@frewsxcv Not sure if bors need to be reminded again with the accidental close 😄 |
frewsxcv
commented
May 20, 2017
should be fine, the PR is still in the queue |
maccoda
commented
May 20, 2017
Ah I did not know that existed. Great thanks! |
bors
commented
May 20, 2017
⌛ Testing commit 55d75c4 with merge 6ee90e3... |
bors
commented
May 20, 2017
💔 Test failed - status-travis |
Any ideas on that one? |
Mark-Simulacrum
commented
May 20, 2017
@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: