-
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 #107463
Rollup of 6 pull requests #107463
Conversation
This works around a bug in git itself; see rust-lang#101144.
…1, r=thomcc Don't re-export private/unstable ArgumentV1 from `alloc`. The `alloc::fmt::ArgumentV1` re-export was marked as `#[stable]` even though the original `core::fmt::ArgumentV1` is `#[unstable]` (and `#[doc(hidden)]`). (It wasn't usable though: ``` error[E0658]: use of unstable library feature 'fmt_internals': internal to format_args! --> src/main.rs:4:12 | 4 | let _: alloc::fmt::ArgumentV1 = todo!(); | ^^^^^^^^^^^^^^^^^^^^^^ | = help: add `#![feature(fmt_internals)]` to the crate attributes to enable ``` ) Part of rust-lang#99012
…ark-Simulacrum Pass `branch.{branch}.remote=origin` to `git submodule update` This works around a bug in git itself. Fixes rust-lang#101144.
…=cjgillot Make `unsizing_params_for_adt` into a query Addresses a FIXME in confirmation. r? ``@ghost``
…-Simulacrum Add option to include private items in library docs I need to perform some one-off analysis on libcore, and I wanted to use the unstable JSON rustdoc output to easily do it. Unfortunately, there is currently no way to include unstable items in the library docs. This PR adds support for that, with the off-by-default `build.library-docs-private-items` setting.
…-Simulacrum Fix typo in `{Rc, Arc}::get_mut_unchecked` docs Just a correction in the documentation of `{Rc, Arc}::get_mut_unchecked`.
end entry paragraph with a period (.)
@bors r+ rollup=never p=5 |
⌛ Testing commit da56c44 with merge cdff031be7b13b485212b72cb05cd696ef92f804... |
💔 Test failed - checks-actions |
@bors retry (spurious) |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 3f25e56496 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (fba9f33): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
Successful merges:
alloc
. #101569 (Don't re-export private/unstable ArgumentV1 fromalloc
.)branch.{branch}.remote=origin
togit submodule update
#106106 (Passbranch.{branch}.remote=origin
togit submodule update
)unsizing_params_for_adt
into a query #107146 (Makeunsizing_params_for_adt
into a query){Rc, Arc}::get_mut_unchecked
docs #107452 (Fix typo in{Rc, Arc}::get_mut_unchecked
docs)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup