Skip to content
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

Merged
merged 3 commits into from
May 21, 2017
Merged

Improving std::env docs #42091

merged 3 commits into from
May 21, 2017

Conversation

maccoda
Copy link
Contributor

@maccoda maccoda commented May 18, 2017

Addresses #29351.
Hopefully this addresses the following points:

@rust-highfive
Copy link
Collaborator

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
Copy link
Contributor Author

maccoda commented May 18, 2017

r? @steveklabnik

@rust-highfive rust-highfive assigned steveklabnik and unassigned brson May 18, 2017
@@ -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
Copy link
Contributor Author

@maccoda maccoda May 18, 2017

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?

@frewsxcv
Copy link
Member

[00:43:03] Linkcheck (x86_64-unknown-linux-gnu)
[00:43:04] std/env/fn.join_paths.html:56: broken link - std/env/containing%20an%20error%20message
[00:43:08] thread 'main' panicked at 'found some broken links', /checkout/src/tools/linkchecker/main.rs:49

///
/// 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
Copy link
Member

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...

Copy link
Contributor Author

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.

@shepmaster shepmaster added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label May 19, 2017
@bors
Copy link
Contributor

bors commented May 19, 2017

☔ The latest upstream changes (presumably #42105) made this pull request unmergeable. Please resolve the merge conflicts.

@maccoda
Copy link
Contributor Author

maccoda commented May 20, 2017

@steveklabnik All seems to be good now. Were there any changes you were wanting?

@Mark-Simulacrum
Copy link
Member

Could you squash your commits? Otherwise looks good to me, but @steveklabnik or someone else from doc team should review.

@maccoda
Copy link
Contributor Author

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
Copy link
Member

Looks good to me, thanks for your contribution!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented May 20, 2017

📌 Commit 55d75c4 has been approved by frewsxcv

@Mark-Simulacrum
Copy link
Member

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
Copy link
Member

err... I did not want to close this.

@maccoda
Copy link
Contributor Author

maccoda commented May 20, 2017

@frewsxcv Not sure if bors need to be reminded again with the accidental close 😄

@frewsxcv
Copy link
Member

should be fine, the PR is still in the queue

https://buildbot2.rust-lang.org/homu/queue/rust

@maccoda
Copy link
Contributor Author

maccoda commented May 20, 2017

Ah I did not know that existed. Great thanks!

@bors
Copy link
Contributor

bors commented May 20, 2017

⌛ Testing commit 55d75c4 with merge 6ee90e3...

@bors
Copy link
Contributor

bors commented May 20, 2017

💔 Test failed - status-travis

@maccoda
Copy link
Contributor Author

maccoda commented May 20, 2017

[00:01:11] # configuration written to .config
[00:01:11] #
[00:01:11] + hide_output ct-ng build
[00:01:11] + set +x
[00:01:41] Sat May 20 05:27:24 UTC 2017 - building ...
[00:02:11] Sat May 20 05:27:54 UTC 2017 - building ...
[00:02:41] Sat May 20 05:28:24 UTC 2017 - building ...
[00:03:11] Sat May 20 05:28:54 UTC 2017 - building ...
[00:03:41] Sat May 20 05:29:24 UTC 2017 - building ...
[00:04:11] Sat May 20 05:29:54 UTC 2017 - building ...
[00:04:41] Sat May 20 05:30:24 UTC 2017 - building ...
[00:05:11] Sat May 20 05:30:54 UTC 2017 - building ...
[00:05:41] Sat May 20 05:31:24 UTC 2017 - building ...
[00:05:57] ERROR: An error was encountered with the build.
[INFO ]  Performing some trivial sanity checks
[INFO ]  Build started 20170520.052654
[INFO ]  Building environment variables
[INFO ]  =================================================================
[INFO ]  Retrieving needed toolchain components' tarballs
[ERROR]  
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Retrieving needed toolchain components' tarballs'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: do_isl_get[scripts/build/companion_libs/121-isl.sh@741]
[ERROR]  >>        called from: do_companion_libs_get[scripts/build/companion_libs.sh@15]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@591]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      '/usr/local/share/doc/crosstool-ng/crosstool-ng-1.22.0/B - Known issues.txt'
[ERROR]  
[ERROR]  (elapsed: 4:46.72)

Any ideas on that one?

@Mark-Simulacrum
Copy link
Member

@bors retry

@Mark-Simulacrum Mark-Simulacrum added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels May 20, 2017
Mark-Simulacrum added a commit to Mark-Simulacrum/rust that referenced this pull request May 20, 2017
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
bors added a commit that referenced this pull request May 21, 2017
Rollup of 6 pull requests

- Successful merges: #41892, #42062, #42091, #42093, #42098, #42127
- Failed merges:
@bors bors merged commit 55d75c4 into rust-lang:master May 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants