-
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 #104711
Rollup of 6 pull requests #104711
Conversation
…rity, r=eholk Check generics parity before collecting return-position `impl Trait`s in trait The only thing is that this duplicates the error message for number of generics mismatch, but we already deduplicate that error message in Cargo. I could add a flag to delay the error if the reviewer cares. Fixes rust-lang#104281 Also drive-by adds a few comments to the `collect_trait_impl_trait_tys` method, and removes an unused argument from `compare_number_of_generics`.
…md64, r=thomcc Reduce exceptions overallocation on non Windows x86_64 Addressing rust-lang#103894 (comment)
…lowering, r=compiler-errors Create def_id for async fns during lowering r? `@compiler-errors`
…-bindings, r=cjgillot Only declare bindings for if-let guards once per arm Currently, each candidate for a match arm uses separate locals for the bindings in the if-let guard, causing problems (rust-lang#88015) when those branches converge in the arm body. Fixes rust-lang#88015 (🤞)
…pty-hack, r=TaKO8Ki Remove a lifetime resolution hack from `compare_predicate_entailment` This is not needed anymore, probably due to rust-lang#102334 equating the function signatures fully in `collect_trait_impl_trait_tys`. Also, the assertion in in rust-lang#102903 makes sure that this is actually fixed, so I'm pretty confident this isn't needed.
…thomcc disable strict-provenance-violating doctests in Miri Most of these are on deprecated unstable functions anyway. This lets us run the remaining doctests with `-Zmiri-strict-provenance`, which I think is a win. r? `@thomcc`
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: b7463e8bdb In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (66ccf36): 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.
CyclesThis benchmark run did not return any relevant results for this metric. |
Successful merges:
impl Trait
s in trait #104295 (Check generics parity before collecting return-positionimpl Trait
s in trait)compare_predicate_entailment
#104701 (Remove a lifetime resolution hack fromcompare_predicate_entailment
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup