-
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
Internal compiler error "node_id_to_type: no type for node" with save-analysis #37323
Comments
This no longer ICEs, marking E-needstest. |
Add tests for a few issues. Fixes rust-lang#41998 Fixes rust-lang#38381 Fixes rust-lang#37515 Fixes rust-lang#37510 Fixes rust-lang#37508 Fixes rust-lang#37366 Fixes rust-lang#37323 Fixes rust-lang#37051 Fixes rust-lang#36839 Fixes rust-lang#35570 Fixes rust-lang#34373 Fixes rust-lang#34222 Certainly not all of the E-needstest issues right now, but I started to get bored.
This error occurred for me when compiling the code in an intermediate state where I expected errors. It is still a small project so I checked in the offending code here: error: internal compiler error: src/librustc/ty/context.rs:438: node_id_to_type: no type for node note: the compiler unexpectedly panicked. this is a bug. note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports note: rustc 1.21.0 (3b72af9 2017-10-09) running on x86_64-apple-darwin note: run with thread 'rustc' panicked at 'Box', src/librustc_errors/lib.rs:490:8 error: Could not compile To learn more, run the command again with --verbose. |
Compiling the code below with
rustc point2.rs -Zsave-analysis
resulted in an internal compiler error.I've tried to minimize the code. Removing either the derive, the other two structs or fixing the lifetime error in
NestedA
makes the panic disappear.Code
Output with backtrace
Meta
Also occurs with stable (but exact output above is from nightly):
The text was updated successfully, but these errors were encountered: