-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Error compiling with wgpu #112532
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
Comments
Do you mind checking if this still ICEs on the most recent nightly? |
I just did that now, and it looks like the issue is fixed on the latest nightly. (sorry should have tried that in first place!) |
That's weird, because I can repro it (cross-compiling for |
@SNCPlay42 on the latest nightly? |
@compiler-errors yep:
Also the version of winit from the report ( |
Wait, this actually ICEs on stable too and I didn't notice because rustc emitted a bunch of errors after the ICE (?!) |
I've reduced it down to this (which is no longer macOS or aarch64 dependent): pub trait NSWindow: Sized {
unsafe fn frame(self) -> () { unimplemented!() }
unsafe fn setFrame_display_(self, windowFrame: (), display: ()) {}
}
impl NSWindow for () {}
pub struct NSRect {}
use std::ops::Deref;
struct MainThreadSafe<T = ()>(T);
impl<T> Deref for MainThreadSafe<T> {
type Target = T;
fn deref(&self) -> &T { unimplemented!() }
}
pub unsafe fn set_maximized_async(ns_window: ()) {
let ns_window = MainThreadSafe(ns_window);
move || {
unimplemented!() = {
NSWindow::frame(*ns_window);
unimplemented!()
};
ns_window.setFrame_display_(unimplemented!(), 0);
};
} (The assignment to This failed to compile without ICE on 1.69: Regression in rust-lang-ci@7adbb6d (#108687) searched nightlies: from nightly-2023-03-06 to nightly-2023-04-19 bisected with cargo-bisect-rustc v0.6.6Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --start=2023-03-06 --end=2023-04-19 --regress=ice -- check @rustbot label regression-from-stable-to-stable |
Whoops, I seemed to have caused it 😆 I'll look into it! |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-medium |
…ments-twice, r=cjgillot Don't record adjustments twice in `note_source_of_type_mismatch_constraint` We call `lookup_method` a few times in `note_source_of_type_mismatch_constraint`, but that function has side-effects to the typeck results. Replace it with a less side-effect-y variant of the function for use in diagnostics. Specifically the ICE in rust-lang#112532 happens because we're recording deref adjustments twice for a call receiver, which causes `ExprUseVisitor` to be angry. Fixes rust-lang#112532
Code
No user code, just trying to compile my project.
The
Cargo.toml
isMeta
rustc --version --verbose
:Error output
The text was updated successfully, but these errors were encountered: