-
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
core::fmt::rt::Opaque
not Sync
caused future compile fail on nightly-2024-03-09
#122674
Comments
if you use the latest version of cargo-bisect-rustc it will bisect the roll-up for you. |
@Nilstrieb Hi, I'm using the latest version of Here's the complete log:
|
It does bisect to #121563 for me. (With this visitor change in particular e760c44#diff-8b601779832d29e42b24bb88ccc3a5762217d72f148e8070767ee787b271190c) |
…errors Do not eat nested expressions' results in `MayContainYieldPoint` format args visitor rust-lang#121563 unintentionally changed the `MayContainYieldPoint` format args visitor behavior, now missing yield points in nested expressions, as seen in rust-lang#122674. The walk can find a yield point in an expression but it was ignored. r? `@petrochenkov` as the reviewer of rust-lang#121563 cc `@Jarcho` as the author Fixes rust-lang#122674. We're in the 1.77 release week. rust-lang#121563 will land on 1.78 but beta is still 1.77.9: this PR will likely need to be backported soon after beta is cut.
Rollup merge of rust-lang#122680 - lqd:nested-await-args, r=compiler-errors Do not eat nested expressions' results in `MayContainYieldPoint` format args visitor rust-lang#121563 unintentionally changed the `MayContainYieldPoint` format args visitor behavior, now missing yield points in nested expressions, as seen in rust-lang#122674. The walk can find a yield point in an expression but it was ignored. r? ``@petrochenkov`` as the reviewer of rust-lang#121563 cc ``@Jarcho`` as the author Fixes rust-lang#122674. We're in the 1.77 release week. rust-lang#121563 will land on 1.78 but beta is still 1.77.9: this PR will likely need to be backported soon after beta is cut.
The fix has landed on master. Reopening to track beta backport. |
@lqd Hi, 1.77.0 has been released, can this be backported to beta now? |
I wasn’t at the weekly meeting and I don’t know for sure: #122680 is not yet marked as accepted for backport (it may just be an oversight in labeling, I’ll try to find out). Once that is done though, the release team, I believe, will backport it. |
updated labels on #122680 (sorry for the delay) |
That was backported in #123172. |
Code
https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=33a2a5c86f6e3276da4da323ac28ed31
Version with regression
searched nightlies: from nightly-2024-03-07 to nightly-2024-03-10
regressed nightly: nightly-2024-03-09
searched commit range: 9c3ad80...46b180e
regressed commit: a655e64
bisected with cargo-bisect-rustc v0.6.8
Host triple: aarch64-apple-darwin
Reproduce with:
@rustbot modify labels: +regression-from-stable-to-nightly -regression-untriaged
The text was updated successfully, but these errors were encountered: