-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 #86626
Rollup of 6 pull requests #86626
Conversation
Due to the std/alloc split, it is not possible to make `alloc::collections::TryReserveError::AllocError` non-exhaustive without having an unstable, doc-hidden method to construct (which negates the benefits from `#[non_exhaustive]`.
Commit e629381 removes the only place these members variables are actually read.
Add `go_to_first` query param to jump to first result Fixes rust-lang#84214 Note that while the issue initially wanted to navigate to an entry on exact match, the discussion settled on using a query parameter (`&go_to_first=true`) instead, regardless of exact or partial match. Demonstration is attached https://user-images.githubusercontent.com/4934853/120258768-7ff28980-c247-11eb-8c8f-1a2ceb242788.mp4
…tsakis Change how edition based future compatibility warnings are handled This fixes rust-lang#85894 by updating how future compatibility lints work. This makes it more apparent that future compatibility warnings can happen for several different reasons. For now `FutureCompatibilityReasons` are limited to three reasons, but we can easily add more. This also updates the generated warning for FCW's that signal code that will error in a future edition. This makes the diagnostics between FCWs at edition boundaries more distinct from those not happening at an edition boundary. r? `@m-ou-se`
…=danielhenrymantilla Rustdoc: Do not list impl when trait has doc(hidden) Fixes rust-lang#86448.
Use `#[non_exhaustive]` where appropriate Due to the std/alloc split, it is not possible to make `alloc::collections::TryReserveError::AllocError` non-exhaustive without having an unstable, doc-hidden method to construct (which negates the benefits from `#[non_exhaustive]`). `@rustbot` label +C-cleanup +T-libs +S-waiting-on-review
…, r=jyn514 chore(rustdoc): remove unused members of RenderType PR rust-lang#86561 removes the only place the `generics` member is read. This PR does even more cleanup.
…r=Amanieu Update compiler-builtins r? `@Amanieu`
@bors r+ rollup=never p=6 |
📌 Commit fac113a has been approved by |
⌛ Testing commit fac113a with merge 87f62f38dade77b900d64245653730959e891c03... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Looks like the tests are interpreting my URL code snippet in the rustdoc book as rust code and trying to run it. I bet there's a way to make it ignore the code block, I'll do some digging. |
Successful merges:
go_to_first
query param to jump to first result #85876 (Addgo_to_first
query param to jump to first result)#[non_exhaustive]
where appropriate #86592 (Use#[non_exhaustive]
where appropriate)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup