-
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
Upgrading nightly introduces compiler panic at visit_opaque_types #58817
Comments
Is the source of your crate available somewhere? Do you use any unstable features? Might be existential type related |
@oli-obk my crate is not public (it has a lot of private code) but it does have these flags on
I could give you a copy of the code through private means if that helps. |
@xrl, impl Trait in bindings is badly broken right now, sorry. I’m going to be reworking it over the coming weeks. I suggest you don’t use it for now. |
I just pulled down the latest nightly and rebuilt, no ICE on compile. I think this is good to close! |
I made a mistake! I thought just running "rustup update" was enough but I guess rustup was pinned to the "stable" nightly |
The error with updated nightly:
|
@alexreg I found the offending bit of code by process of elimination:
replacing this code with |
Closing as an actionable MCVE could not be provided |
I did a
rustup update
and the new nightly started failing to compile.I tried this code:
I don't have a good way of minimal reproduction on my medium-size codebase. But I did figure out another rustup nightly that would stop seeing the error.
I expected to see this happen:
rustup default nightly; rustup update; cargo build
should have kept workingInstead, this happened:
maybe my cargo file will help? nothing fancy going on there:
I can fix this by downgrading:
rustup default nightly-2019-02-19
and thencargo build
works again. The error starts happening onrustup default nightly-2019-02-21
.Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: