Internal Error?

help
1 
encountered while trying to mark dependency green: typeck(402a0d6024cae446-4889019bb23ae30c)
encountered while trying to mark dependency green: typeck_item_bodies(0-0)
For more information about this error, try `rustc --explain E0432`.
warning: `grob` (example "username") generated 8 warnings
error: could not compile `grob` due to previous error; 8 warnings emitted

Are those first two messages the result of an internal compiler error?

2

Without other information, I believe it is in fact an internal issue with the compiler. Please file an issue, ideally with the code sufficient to reproduce it.

2 Likes
3

Thank you for the reply.

I believe it's triggered by an unresolved external which is the E0432 in the third message.

I've committed and tagged so I can hopefully return to the snapshot that triggers the behaviour.

For posterity...

rustc --version
rustc 1.69.0 (84c898d65 2023-04-16)

cargo version
cargo 1.69.0 (6e9a83356 2023-04-12)

Here?

4

Yes.

1 Like
5

So I never lose this...

  • Windows 10
  • Check out internal-compiler-error-001
  • Build
  • Rename WindowsWriteBuffer7 to WindowsWriteBuffer in traits.rs, lib.rs, and buffer.rs
  • Build
  • Rename WindowsWriteBuffer to WindowsWriteBuffer7 in traits.rs, lib.rs, and buffer.rs
  • Build

I suspect the bug is triggered by a missing dependency check; that the artifacts for an example are not being rebuilt after the library is rebuilt. The internal errors disappear after a cargo clean.

6

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.