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

Expand std::path::Component documentation. #34475

Merged
merged 1 commit into from
Jun 28, 2016

Conversation

frewsxcv
Copy link
Member

Indicate how it gets created and add an example.

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

@frewsxcv
Copy link
Member Author

r? @GuillaumeGomez

@@ -525,6 +525,26 @@ impl<'a> Hash for PrefixComponent<'a> {
///
/// See the module documentation for an in-depth explanation of components and
/// their role in the API.
///
/// This `struct` is created from iterating over the [`path::Components`]
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 sure to understand in here. You're talking about the Components struct but this is supposed to be the doc for the Component enum. Any further explanation please? :)

Copy link
Member Author

Choose a reason for hiding this comment

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

The only way (that I know) to create a Component struct is by iterating over the Components struct.

Copy link
Member Author

Choose a reason for hiding this comment

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

Nevermind. I'll change this to enum later.

Copy link
Member

Choose a reason for hiding this comment

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

So it was just the wrong word. Ping me once changed then. 😛

Copy link
Member Author

Choose a reason for hiding this comment

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

Ping.

Indicate how it gets created and add an example.
@GuillaumeGomez
Copy link
Member

All good, thanks!

@bors: r+ rollup

@bors
Copy link
Contributor

bors commented Jun 27, 2016

📌 Commit f1d600c has been approved by GuillaumeGomez

steveklabnik added a commit to steveklabnik/rust that referenced this pull request Jun 27, 2016
…eGomez

Expand `std::path::Component` documentation.

Indicate how it gets created and add an example.
steveklabnik added a commit to steveklabnik/rust that referenced this pull request Jun 27, 2016
…eGomez

Expand `std::path::Component` documentation.

Indicate how it gets created and add an example.
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Jun 28, 2016
…eGomez

Expand `std::path::Component` documentation.

Indicate how it gets created and add an example.
bors added a commit that referenced this pull request Jun 28, 2016
@bors bors merged commit f1d600c into rust-lang:master Jun 28, 2016
@frewsxcv frewsxcv deleted the path-component branch October 2, 2016 23:06
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.

5 participants