-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 8 pull requests #100356
Rollup of 8 pull requests #100356
Conversation
This reflects the concensus from the libs team as reported at rust-lang#70887 (comment) Co-authored-by: Yosh Wuyts <github@yosh.is>
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Stabilize backtrace This PR stabilizes the std::backtrace module. As of rust-lang#99431, the std::Error::backtrace item has been removed, and so the rest of the backtrace feature is set to be stabilized. Previous discussion can be found in rust-lang#72981, rust-lang#3156. Stabilized API summary: ```rust pub mod std { pub mod backtrace { pub struct Backtrace { } pub enum BacktraceStatus { Unsupported, Disabled, Captured, } impl fmt::Debug for Backtrace {} impl Backtrace { pub fn capture() -> Backtrace; pub fn force_capture() -> Backtrace; pub const fn disabled() -> Backtrace; pub fn status(&self) -> BacktraceStatus; } impl fmt::Display for Backtrace {} } } ``` `@yaahc`
…oerister Add error if link_ordinal used with unsupported link kind The `link_ordinal` attribute only has an affect if the `raw-dylib` link kind is used, so add an error if it is used with any other link kind.
…eiser Add more `// unit-test`s to MIR opt tests I only changed things which are hopefully completely uninteresting. I plan to submit more PRs that cover more files, but those cases will need some more complicated (and hence possibly controversial) changes, so I'll try and submit those in reasonably sized batches. r? rust-lang/wg-mir-opt
Rename integer log* methods to ilog* This reflects the concensus from the libs team as reported at rust-lang#70887 (comment). Joint work with `@yoshuawuyts.`
…before-array, r=fee1-dead Suggest a missing semicolon before an array fixes rust-lang#99658
…errors Iterate generics_def_id_map in reverse order to fix P-critical issue Closes rust-lang#100187 Fixes a `P-critical` beta regression.
…oc, r=joshtriplett docs: remove repetition in `is_numeric` function docs In rust-lang#99628 we introduce new docs for the `is_numeric` function, and this is a follow-up PR that removes some unnecessary repetition that may be introduced by some rebasing. `@rustbot` r? `@joshtriplett`
@bors r+ rollup=never p=8 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Tested on commit rust-lang/rust@1603a70. Direct link to PR: <rust-lang/rust#100356> 💔 miri on windows: test-pass → test-fail (cc @oli-obk @RalfJung). 💔 miri on linux: test-pass → test-fail (cc @oli-obk @RalfJung).
Finished benchmarking commit (1603a70): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesThis benchmark run did not return any relevant results for this metric. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Update cargo 7 commits in 4fd148c47e733770c537efac5220744945d572ef..ce40690a5e4e315d3dab0aae1eae69d0252c52ac 2022-08-03 15:03:52 +0000 to 2022-08-09 22:32:17 +0000 - Make the `rust-version` error recommend `cargo update --precise -p crate@ver` (rust-lang/cargo#10891) - resolver docs: link to version requirements syntax full explanation (rust-lang/cargo#10946) - Bump os_info to 3.5.0 (rust-lang/cargo#10943) - Mark --timings=html unstable in the document (rust-lang/cargo#10941) - Mention that aliases are recursive (rust-lang/cargo#10935) - Test if reserved filenames are allowed in Windows (rust-lang/cargo#10322) - improve error message for `no such subcommand` (rust-lang/cargo#10924)
📌 Perf builds for each rolled up PR:
In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
// unit-test
s to MIR opt tests #100086 (Add more// unit-test
s to MIR opt tests)is_numeric
function docs #100345 (docs: remove repetition inis_numeric
function docs)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup