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

Rollup of 6 pull requests #41395

Closed
wants to merge 17 commits into from
Closed

Rollup of 6 pull requests #41395

wants to merge 17 commits into from

Conversation

lukaramu and others added 17 commits April 15, 2017 23:55
Part of rust-lang#29368.
* added missing links
* updated method summaries to use 3rd person style
* added missing periods in `Component`'s variant summaries
* use standard iterator boilerplate in `Components`' and `Iter`'s docs
* added example to `Iter::as_path`, adapted from `Components::as_path`'s
  example
* consolidated examples for `Path::file_name`
* some other small fixes
Part of rust-lang#29368.
* Added a new summary paragraph about std::path's parsing facilities
* Slightly exanded `Component`'s docs
* removed the now redundant section on component types from the module docs
* moved the section on path normalization during parsing to the docs on
  `Path::components`
* Clarified difference between `Prefix` and `PrefixComponent` in their
  respecive summary sentences
Part of rust-lang#29368.
* Added explanation for why the struct exists
* Added link to where it is created
* Added example
* Closed an unclosed paren
* seperator -> separator
* deperator -> separator
Previously the `cargotest` suite would run some arbitrary revision of Cargo's
test suite, but now that we're bundling it in tree we should be running the
Cargo submodule's test suite instead.
These show up in rustdoc so need to be correct.
cc rust-lang#32730 -- I left exactly one instance where I wasn't sure of the
right behavior.
Improve std::path docs

Fixes rust-lang#29368.

This PR contains a pretty significant redistribution of some of the module docs to more appropriate places, as well as general expansion, clarification, and additional examples.

For more details, see the commit descriptions.

r? @steveklabnik
Run tests for the cargo submodule in tree

Previously the `cargotest` suite would run some arbitrary revision of Cargo's
test suite, but now that we're bundling it in tree we should be running the
Cargo submodule's test suite instead.
update mdbook

Ship some more improvements.

r? @rust-lang/docs
…nce, r=eddyb

Fix ICE building gluon_vm

The problem was due to various places we were failing to propagate obligations. I think I got them mostly correct, but I didn't get around to writing test cases for each case.

r? @eddyb or @arielb1
Fix a few stability attributes

These show up in rustdoc so need to be correct.
remove disclaimer from bootstrap/README.md
@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 @sfackler (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

@bors r+ p=10

@bors
Copy link
Contributor

bors commented Apr 19, 2017

📌 Commit 6bdf84d has been approved by frewsxcv

@bors
Copy link
Contributor

bors commented Apr 19, 2017

⌛ Testing commit 6bdf84d with merge 084a9da...

@aidanhs aidanhs added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Apr 19, 2017
@bors
Copy link
Contributor

bors commented Apr 19, 2017

💔 Test failed - status-travis

@aidanhs
Copy link
Member

aidanhs commented Apr 19, 2017

[00:51:18] Initialized empty Git repository in /checkout/obj/build/ct/xsv/.git/
[00:51:18] fatal: Could not parse object 'a9a7163f2a2953cea426fee1216bec914fe2f56a'.
[00:51:19] From https://github.com/BurntSushi/xsv
[00:51:19]  * branch            master     -> FETCH_HEAD
[00:51:19] fatal: Could not parse object 'a9a7163f2a2953cea426fee1216bec914fe2f56a'.
[00:51:19] From https://github.com/BurntSushi/xsv
[00:51:19]  * branch            master     -> FETCH_HEAD
[00:51:19] fatal: Could not parse object 'a9a7163f2a2953cea426fee1216bec914fe2f56a'.
[00:51:20] From https://github.com/BurntSushi/xsv
[00:51:20]  * branch            master     -> FETCH_HEAD
[00:51:20] HEAD is now at a9a7163 Merge pull request #53 from alexcrichton/fix-beta
[00:51:20] error: An unknown error occurred

Now that's interesting, we've seen this before (ctrl+f "corrupt download" on #40474) but on appveyor.

Spurious though.

@frewsxcv frewsxcv closed this Apr 19, 2017
@frewsxcv frewsxcv reopened this Apr 19, 2017
@frewsxcv
Copy link
Member Author

@bors retry

@bors
Copy link
Contributor

bors commented Apr 19, 2017

⌛ Testing commit 6bdf84d with merge 8eeba27...

@bors
Copy link
Contributor

bors commented Apr 19, 2017

💔 Test failed - status-travis

@aidanhs
Copy link
Member

aidanhs commented Apr 19, 2017

Basically blocked on #41398.

@frewsxcv
Copy link
Member Author

I'll open a new rollup with that

@frewsxcv frewsxcv closed this Apr 19, 2017
@Centril Centril added the rollup A PR which is a rollup label Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup 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.