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

Stricter doctests for corelibs #29544

Merged
merged 17 commits into from
Nov 12, 2015
Merged

Conversation

Ryman
Copy link
Contributor

@Ryman Ryman commented Nov 3, 2015

Did this alphabetically, so I didn't see how std was doing things till I was nearly finished. If you prefer to add crate-level-whitelists like std instead of test-level, I can rebase with that strategy.

A number of these commits can probably be dropped as the crates don't have much to test, and are deprecated. Let me know which if any to drop! (can also squash after review if desired)

r? @steveklabnik

@steveklabnik
Copy link
Member

This looks great, thanks! I love the idea of making these more strict, I just didn't take the time to do it myself.

I'm going to merge as-is. I'm in the middle of going through the whole stdlib docs anyway, so if I want to make changes, I will do so then. This looks great for now. And keeping the commits split per library seems fine as well.

@steveklabnik
Copy link
Member

@bors: r+ rollup

@bors
Copy link
Contributor

bors commented Nov 10, 2015

📌 Commit 956986a has been approved by steveklabnik

@steveklabnik
Copy link
Member

(sorry for the long review delay, as well :/)

steveklabnik added a commit to steveklabnik/rust that referenced this pull request Nov 10, 2015
…labnik

Did this alphabetically, so I didn't see [how `std` was doing things](https://dxr.mozilla.org/rust/source/src/libstd/lib.rs#215) till I was nearly finished. If you prefer to add crate-level-whitelists like std instead of test-level, I can rebase with that strategy.

A number of these commits can probably be dropped as the crates don't have much to test, and are deprecated. Let me know which if any to drop! (can also squash after review if desired)

r? @steveklabnik
@bors
Copy link
Contributor

bors commented Nov 10, 2015

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

bors added a commit that referenced this pull request Nov 10, 2015
@steveklabnik
Copy link
Member

@Ryman you sent me a message on IRC, but you're not on now. Just a rebase is fine :)

@Ryman Ryman force-pushed the reduce_doc_warnings branch from 956986a to 5ae1937 Compare November 12, 2015 06:44
@Ryman
Copy link
Contributor Author

Ryman commented Nov 12, 2015

@steveklabnik rebased (and removed liblibc commit as it should be done on crates.io repo now)!

@steveklabnik
Copy link
Member

@bors: r+ p=1

@bors
Copy link
Contributor

bors commented Nov 12, 2015

📌 Commit 5ae1937 has been approved by steveklabnik

@bors
Copy link
Contributor

bors commented Nov 12, 2015

⌛ Testing commit 5ae1937 with merge 8c9c951...

bors added a commit that referenced this pull request Nov 12, 2015
Did this alphabetically, so I didn't see [how `std` was doing things](https://dxr.mozilla.org/rust/source/src/libstd/lib.rs#215) till I was nearly finished. If you prefer to add crate-level-whitelists like std instead of test-level, I can rebase with that strategy.

A number of these commits can probably be dropped as the crates don't have much to test, and are deprecated. Let me know which if any to drop! (can also squash after review if desired)

r? @steveklabnik
@steveklabnik
Copy link
Member

(giving priority since this touches a lot of things)

@steveklabnik
Copy link
Member

(but i guess the queue is already empty so)

@bors bors merged commit 5ae1937 into rust-lang:master Nov 12, 2015
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.

3 participants