-
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 #105804
Rollup of 6 pull requests #105804
Conversation
https://reviews.llvm.org/D140192 caused the LLVM variable generated for enum discriminant checks to be named differently (%narrow vs %1). This adjusts the test CHECK directives to match any name.
Help rust-analyzer normalize query return types See [zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/rustc.20query.20types.20are.20not.20normalized.20since.20recently/near/312686086), since rust-lang#103808, rust analyzer doesn't normalize return types of queries. This is because r-a doesn't support associated type defaults (yet). The easiest fix is to not use associated type defaults (duh), which this PR does. r? `@cjgillot`
…t, r=eholk Don't bug if we're trying to cast `dyn*` to another type Fixes rust-lang#105097
…errors, r=eholk bail in `collect_trait_impl_trait_tys` if signatures reference errors Fixes rust-lang#105290
Detect inherent associated types not having CamelCase Fixes rust-lang#105341.
…notriddle rustdoc: Don't add "Read more" link if there is no extra content Fixes rust-lang#105677.
…miasko Make enum-match.rs test robust against variable name changes https://reviews.llvm.org/D140192 caused the LLVM variable generated for enum discriminant checks to be named differently (%narrow vs %1). This adjusts the test CHECK directives to match any name.
@bors r+ rollup=never p=6 |
⌛ Testing commit 803ce45 with merge 107aed98b370ce9ec648e8a0d35cca89c55159d0... |
💔 Test failed - checks-actions |
@bors retry network failure |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: bbb9cfbbc5 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (998e1a9): 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.
|
Successful merges:
dyn*
to another type #105710 (Don't bug if we're trying to castdyn*
to another type)collect_trait_impl_trait_tys
if signatures reference errors #105711 (bail incollect_trait_impl_trait_tys
if signatures reference errors)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup