-
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
nightly 2022-06-29 rejects previously compiling code with missing trait implementations #99536
Comments
Started attempting to find a minimal reproduction; this playground does not reproduce the issue, so clearly there is something more complex involved than just returning an |
Guessing it's #97346 |
@hawkw, are there rustdocs for edit: nvm i just built them myself. |
Soooooo, I think I got it to compile. This is not a correct soltuion, because it causes a bunch of UI tests to fail. Draft PR: #99547 This has to do with the fact that when we This means that when we later side-note: does it usually take 3 minutes to compile |
That's on purpose. The only time we don't do that is for return types so that we can merge the types from all the return sites. how did we miss this in the crater run :/ |
@oli-obk linkerd isn't on crates.io i think? 🤔 |
we run github crates, too, and I was certain I have seen linkerd in crater reports before |
uhm... did crater not recognize the regression because it hit a also it seems like it didn't actually run on the sub-crates like nominating for t-types discussion, as there was a regression we didn't know about. I think what all users that hit this desire is not actually |
|
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-high |
Let's revert for now, this seems more useful in practice than we thought |
yes 🥲 |
Btw starting to see this in beta now as well. https://github.com/tower-rs/tower/runs/7789919663?check_suite_focus=true |
Thanks, yeah, there is a revert PR in flight but the author is on vacation. In the mean time, I've beta-backport nominated the revert PR and that'll likely get approved, fixing this in a few more weeks. Sorry for the delay. |
No problem! Thanks for the quick response 😄 |
Revert "Rollup merge of rust-lang#97346 - JohnTitor:remove-back-compat-hacks, … …r=oli-obk" This reverts commit c703d11, reversing changes made to 64eb9ab. it didn't apply cleanly, so now it works the same for RPIT and for TAIT instead of just working for RPIT, but we should keep those in sync anyway. It also exposed a TAIT bug (see the feature gated test that now ICEs). r? `@pnkfelix` fixes rust-lang#99536
Code
The
linkerd2-proxy
project fails to compile on nighty 2022-06-29 and later due to a "missing" implementation of a trait in animpl Trait
return value. The same code compiles successfully on stable and on prior nightlies. The error occurs when usingimpl Trait
as an associated type of a return value that is itself animpl Trait
, when the associated type has trait bounds placed on it by the outerimpl Trait
.An error like this is generated:
Unfortunately, I don't have a minimal reproducer yet; I'd like to find one, but for now, checking out linkerd/linkerd2-proxy@0288b9c and running
cargo +nigihtly-2022-06-29 build
will fail with this error.Version it worked on
The most recent nightly that can compile the
linkerd2-proxy
codebase successfully is2022-06-28
. Successful CI build: https://github.com/linkerd/linkerd2-proxy/runs/7088482069?check_suite_focus=trueVersion with regression
Nightly
2022-06-29
and later fails to compile the same codebase. Failing CI build: https://github.com/linkerd/linkerd2-proxy/runs/7107925369?check_suite_focus=trueWe ran
cargo bisect-rustc
and it appears that commit 00ebeb8 introduced the regression.searched nightlies: from nightly-2022-06-28 to nightly-2022-06-30
regressed nightly: nightly-2022-06-29
searched commit range: 2f3ddd9...8308806
regressed commit: 00ebeb8
bisected with cargo-bisect-rustc v0.6.3
Host triple: x86_64-unknown-linux-gnu
Reproduce with:
The text was updated successfully, but these errors were encountered: