-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Use LazyLock
to lazily resolve backtraces
#109075
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
7dfec9e
to
e9e5af3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but still probably needs T-libs
approval ❤️
☔ The latest upstream changes (presumably #106152) made this pull request unmergeable. Please resolve the merge conflicts. |
e9e5af3
to
6776af5
Compare
Soon™ |
@rustbot author |
@rustbot ready |
Neat! Looks good to me. |
…ngjubilee Use `LazyLock` to lazily resolve backtraces By using TAIT to name the initializing closure, `LazyLock` can be used to replace the current `LazilyResolvedCapture`.
…kingjubilee Rollup of 4 pull requests Successful merges: - rust-lang#95965 (Stabilize const-weak-new) - rust-lang#109075 (Use `LazyLock` to lazily resolve backtraces) - rust-lang#113741 (Don't install default projection bound for return-position `impl Trait` in trait methods with no body) - rust-lang#114268 (Fix empty_write since rust version attribute) r? `@ghost` `@rustbot` modify labels: rollup
By using TAIT to name the initializing closure,
LazyLock
can be used to replace the currentLazilyResolvedCapture
.