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

Update ChildStderr docs to be clearer #40829

Merged
merged 2 commits into from
Apr 9, 2017
Merged

Update ChildStderr docs to be clearer #40829

merged 2 commits into from
Apr 9, 2017

Conversation

mgattozzi
Copy link
Contributor

Before the docs only had a line about where it was found and that it was
a handle to stderr. This commit changes it so that the summary second line is
removed and that it's a bit clearer about what can be done with it. Part of
#29370

Before the docs only had a line about where it was found and that it was
a handle to stderr. This commit changes it so that the summary second line is
removed and that it's a bit clearer about what can be done with it. Part of
\#29370
@mgattozzi
Copy link
Contributor Author

r? @steveklabnik

@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 @BurntSushi (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.

@mgattozzi
Copy link
Contributor Author

@steveklabnik I'm not sure if this is what you meant by expanding upon the docs in #29370. If it is great because I have two PRs ready to go for ChildStdin and ChildStdout, but I figured it best to get a sense for what you wanted this to be expanded too here before opening those two.

@@ -233,8 +233,9 @@ impl fmt::Debug for ChildStdout {
}
}

/// A handle to a child process's stderr. This struct is used in the [`stderr`]
/// field on [`Child`].
/// A handle to a child process's stderr. It can be used to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep "This struct is used in the [stderr] field on [Child]."

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not saying to remove it, I'm saying that there needs to be whitespace between.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay will do. That makes more sense.

@@ -233,8 +233,9 @@ impl fmt::Debug for ChildStdout {
}
}

/// A handle to a child process's stderr. This struct is used in the [`stderr`]
/// field on [`Child`].
/// A handle to a child process's stderr. It can be used to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So what we need is a newline between this sentence and the next. rustdoc treats the first paragraph as the summary so

/// A handle to a child process' stderr.
///
/// It can be used to....

that kind of thing. make sense?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to have it this way as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahhhh okay got it.

@@ -233,8 +233,9 @@ impl fmt::Debug for ChildStdout {
}
}

/// A handle to a child process's stderr. This struct is used in the [`stderr`]
/// field on [`Child`].
/// A handle to a child process's stderr. It can be used to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not saying to remove it, I'm saying that there needs to be whitespace between.

@steveklabnik
Copy link
Member

wow thanks github, dunno how that got duplicated...

@mgattozzi
Copy link
Contributor Author

I see what your wording in the issue means now. After my other PR is done building locally I can move on to this one.

@mgattozzi
Copy link
Contributor Author

@GuillaumeGomez and @steveklabnik I've updated the docs to have the newlines and changed it back to the original wording as requested!

@steveklabnik
Copy link
Member

@bors: r+ rollup

@bors
Copy link
Contributor

bors commented Apr 9, 2017

📌 Commit c7f2dbe has been approved by steveklabnik

@bors
Copy link
Contributor

bors commented Apr 9, 2017

⌛ Testing commit c7f2dbe with merge fa332c9...

bors added a commit that referenced this pull request Apr 9, 2017
Update ChildStderr docs to be clearer

Before the docs only had a line about where it was found and that it was
a handle to stderr. This commit changes it so that the summary second line is
removed and that it's a bit clearer about what can be done with it. Part of
#29370
@bors
Copy link
Contributor

bors commented Apr 9, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: steveklabnik
Pushing fa332c9 to master...

@bors bors merged commit c7f2dbe into rust-lang:master Apr 9, 2017
@mgattozzi
Copy link
Contributor Author

Awesome! I'll get the other two in soon so that we can knock them off the process list.

@mgattozzi mgattozzi deleted the ChildStderr branch April 9, 2017 20:40
frewsxcv added a commit to frewsxcv/rust that referenced this pull request May 3, 2017
…eveklabnik

Update ChildStdin/ChildStdout docs to be clearer

This is part of rust-lang#29370 and continues the work from rust-lang#40829
frewsxcv added a commit to frewsxcv/rust that referenced this pull request May 3, 2017
…eveklabnik

Update ChildStdin/ChildStdout docs to be clearer

This is part of rust-lang#29370 and continues the work from rust-lang#40829
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants