-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Rollup of 3 pull requests #150500
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 3 pull requests #150500
Conversation
…dtolnay Implement `TryFrom<char>` for `usize`. Feature gate: `usize_try_from_char`. This PR implements `TryFrom<char>` for `usize`. `usize` is currently the only, unsigned, integral type to not implement `TryFrom<char>`. Technically, this conversion is trivial and can already be expressed with some indirection. I think it useful to be able to describe this set of types with this interface.
…pratt Mark set_times as unavailable for RTEMS target This PR just updates one of the config switches to exclude `utimesat` for the RTEMS target. This currently creates undefined reference errors when building the target. With this fix applied it also needs a fix in libc (see rust-lang/libc#4875) which will hopefully be available in release 0.2.179.
mir_build: Remove several remnants of `#![feature(inline_const_pat)]`
This PR cleans up some THIR-related code that was only needed for inline `const { .. }` blocks in patterns. The `inline_const_pat` feature was removed in rust-lang#138492 due to implementation concerns.
I considered retaining the code for preserving `ExpandedConstant` for range endpoints, but ultimately decided to remove that too, because I found it very awkward to document an edge case that is currently not needed by any subsequent code.
With this PR, `is_const_pat_that_looks_like_binding` is the only function that meaningfully consumes `thir::PatKind::ExpandedConst`.
|
@bors r+ rollup=never p=3 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: d874dce125 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing d874dce (parent) -> d465f99 (this PR) Test differencesShow 24 test diffs24 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard d465f990431b951f5b2d69aa499606db4b3ea359 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (d465f99): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 2.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 482.826s -> 482.641s (-0.04%) |
Successful merges:
TryFrom<char>forusize. #146792 (ImplementTryFrom<char>forusize.)#![feature(inline_const_pat)]#150498 (mir_build: Remove several remnants of#![feature(inline_const_pat)])r? @ghost
@rustbot modify labels: rollup
Create a similar rollup