-
Notifications
You must be signed in to change notification settings - Fork 13k
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 4 pull requests #114272
Rollup of 4 pull requests #114272
Conversation
Bump its stabilization version several times along the way to accommodate changes in release processes. Co-authored-by: Mara Bos <[email protected]> Co-authored-by: Trevor Gross <[email protected]>
Stabilize const-weak-new This is a fairly uncontroversial library stabilization, so I'm going ahead and proposing it to ride the trains to stable. This stabilizes the following APIs, which are defined to be non-allocating constructors. ```rust // alloc::rc impl<T> Weak<T> { pub const fn new() -> Weak<T>; } // alloc::sync impl<T> Weak<T> { pub const fn new() -> Weak<T>; } ``` Closes rust-lang#95091 ``@rustbot`` modify labels: +needs-fcp
…ngjubilee Use `LazyLock` to lazily resolve backtraces By using TAIT to name the initializing closure, `LazyLock` can be used to replace the current `LazilyResolvedCapture`.
…-missing-opaque, r=spastorino Don't install default projection bound for return-position `impl Trait` in trait methods with no body This ensures that we never try to project to an opaque type in a trait method that has no body to infer its hidden type, which means we never later call `type_of` on that opaque. This is because opaque types try to reveal their hidden type when proving auto traits. I thought about this a lot, and I think this is a fix that's less likely to introduce other strange downstream ICEs than rust-lang#113461. Fixes rust-lang#113434 r? `@spastorino`
Fix empty_write since rust version attribute Fixup of rust-lang#98154 for the rust version. r? ``@workingjubilee``
@bors r+ rollup=never p=4 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: d9feb02e8d In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (dfc9d3f): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
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: 652.627s -> 652.418s (-0.03%) |
Successful merges:
LazyLock
to lazily resolve backtraces #109075 (UseLazyLock
to lazily resolve backtraces)impl Trait
in trait methods with no body #113741 (Don't install default projection bound for return-positionimpl Trait
in trait methods with no body)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup