d66647ba2c
When the unstable finterprint error was added, Rust was on fire, and we needed a quick way for people to sort of understand what's going on, follow the tracking issue, and leave some information without overwhelming the issue tracker and focusing on getting their code working. This is what motivated the previous message. It called this a "known issue", provided help on how to fix it, and only secondarily asked for a bug report. This is no longer true. These days incremental compilation is fairly solid and these issues are supposed to be rare, we expect *none* of them to exist (but obviously know that's not true). As such, it's time to reword this message. Recently someone mentioned how they didn't bother reporting this issue because it said that it was a "known issue", and I only got awareness of their problem because they complained about all the rustc-ice files hanging around their directories. This is not at all what we want, we want reports from people, ideally with a reproduction. To get this, I reworded the error. It now explicitly asks for a reproduction (and explaining what that means) and no longer calls it a "known issue". It also does not link to the tracking issue anymore, because I don't think this tracking issue is useful. It should probably be closed. I still mention the workaround, but explicitly call it a "workaround". People should report a reproduction and only *then* use the workaround.
31 lines
1.9 KiB
Plaintext
31 lines
1.9 KiB
Plaintext
query_system_cycle = cycle detected when {$stack_bottom}
|
|
.note = see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information
|
|
|
|
query_system_cycle_recursive_trait_alias = trait aliases cannot be recursive
|
|
|
|
query_system_cycle_recursive_ty_alias = type aliases cannot be recursive
|
|
query_system_cycle_recursive_ty_alias_help1 = consider using a struct, enum, or union instead to break the cycle
|
|
query_system_cycle_recursive_ty_alias_help2 = see <https://doc.rust-lang.org/reference/types.html#recursive-types> for more information
|
|
|
|
query_system_cycle_stack_middle = ...which requires {$desc}...
|
|
|
|
query_system_cycle_stack_multiple = ...which again requires {$stack_bottom}, completing the cycle
|
|
|
|
query_system_cycle_stack_single = ...which immediately requires {$stack_bottom} again
|
|
|
|
query_system_cycle_usage = cycle used when {$usage}
|
|
|
|
query_system_increment_compilation = internal compiler error: encountered incremental compilation error with {$dep_node}
|
|
|
|
query_system_increment_compilation_note1 = please follow the instructions below to create a bug report with the provided information
|
|
query_system_increment_compilation_note2 = for incremental compilation bugs, having a reproduction is vital
|
|
query_system_increment_compilation_note3 = an ideal reproduction consists of the code before and some patch that then triggers the bug when applied and compiled again
|
|
query_system_increment_compilation_note4 = as a workaround, you can run {$run_cmd} to allow your project to compile
|
|
|
|
query_system_overflow_note = query depth increased by {$depth} when {$desc}
|
|
|
|
query_system_query_overflow = queries overflow the depth limit!
|
|
.help = consider increasing the recursion limit by adding a `#![recursion_limit = "{$suggested_limit}"]` attribute to your crate (`{$crate_name}`)
|
|
|
|
query_system_reentrant = internal compiler error: reentrant incremental verify failure, suppressing message
|