-
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 9 pull requests #115615
Rollup of 9 pull requests #115615
Conversation
It uses `once` chained with `(0..self.num_calls).map(...)` followed by `.take(self.num_calls`. I found this hard to read. It's simpler to just use `repeat_with`.
…rgs, r=b-naber Remove the unhelpful let binding diag comes from FormatArguments Fixes rust-lang#114374
…iler-errors Add explanatory note to 'expected item' error Fixes rust-lang#113110 It changes the diagnostic from this: ``` error: expected item, found `5` --> ../test.rs:1:1 | 1 | 5 | ^ expected item ``` to this: ``` error: expected item, found `5` --> ../test.rs:1:1 | 1 | 5 | ^ expected item | = note: items are things that can appear at the root of a module = note: for a full list see https://doc.rust-lang.org/reference/items.html ```
…Nilstrieb Replace `rustc_data_structures` dependency with `rustc_index` in `rustc_parse_format` `rustc_data_structures` is only used for the `static_assert_size` macro, yet that is defined in `rustc_index` and merely re-exported. `rustc_index` is a lot more lightweight than `rustc_data_structures` which would make this a lot more reusable for rust-analyzer.
Clarify cryptic comments Clarifies some unclear comments that lurked in the compiler. r? ``@oli-obk``
fix rust-lang#115348 fix rust-lang#115348 It looks that: - In `rustc_mir_build::build`, the body of function will not be built, when the `tcx.check_match(def)` fails due to `non-exhaustive patterns` - In `rustc_mir_transform::check_unsafety`, the `UnsafetyChecker` collects all `used_unsafe_blocks` in the MIR of a function, and the `UnusedUnsafeVisitor` will visit all `UnsafeBlock`s in the HIR and collect `unused_unsafes`, which are not contained in `used_unsafe_blocks`, and report `unnecessary_unsafe`s - So the unsafe block in the issue example code will be reported as `unnecessary_unsafe`.
A small change A small change I made while poking around the code. r? `@lqd`
…g, r=onur-ozkan Fix log formatting in bootstrap `format!()` was missing, so log was just showing `{target}` verbatim. (I also applied a small clippy suggestion in `builder.info()`)
Better Debug for `Ty` in smir Similar to what I did here rust-lang#115534. r? ``@oli-obk``
Fix minor grammar typo
@bors r+ rollup=never p=9 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: a5b2ac6906 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (4e21162): 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)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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 629.849s -> 628.332s (-0.24%) |
Successful merges:
rustc_data_structures
dependency withrustc_index
inrustc_parse_format
#115574 (Replacerustc_data_structures
dependency withrustc_index
inrustc_parse_format
)unsafe
keywords marked as unnecessary when inside incomplete match #115348)Ty
in smir #115605 (Better Debug forTy
in smir)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup