diagnostic emitted due to `-Z deduplicate-diagnostics=no`aan'_(impossible to capture backtrace where this happened)Backtraces are currently disabled: set `RUST_BACKTRACE=1` and re-run to see where it happened.This happened in the following `must_produce_diag` call's backtrace: `trimmed_def_paths` called, diagnostics were expected but none were emitted. Use `with_no_trimmed_paths` for debugging. assertion failed: !self.substitutions.is_empty()assertion failed: !lines.lines.is_empty() || bounding_span.is_dummy()error: internal compiler errorwarningfailure-noteerrors_delayed_at_without_newlineerrors_delayed_at_with_newlineemitted_atRUST_BACKTRACEno errors encountered even though delayed bugs were createdthose delayed bugs will now be shown as internal compiler errorsdelayed bug: errors_invalid_flushed_delayed_diagnostic_levelassertion failed: self.stashed_diagnostics.is_empty()errors_delayed_at_with_newline = delayed at {$emitted_at} {$note} errors_delayed_at_without_newline = delayed at {$emitted_at} - {$note} errors_expected_lifetime_parameter = expected lifetime {$count -> [1] parameter *[other] parameters } errors_indicate_anonymous_lifetime = indicate the anonymous {$count -> [1] lifetime *[other] lifetimes } errors_invalid_flushed_delayed_diagnostic_level = `flushed_delayed` got diagnostic with level {$level}, instead of the expected `DelayedBug` errors_target_inconsistent_architecture = inconsistent target specification: "data-layout" claims architecture is {$dl}-endian, while "target-endian" is `{$target}` errors_target_inconsistent_pointer_width = inconsistent target specification: "data-layout" claims pointers are {$pointer_size}-bit, while "target-pointer-width" is `{$target}` errors_target_invalid_address_space = invalid address space `{$addr_space}` for `{$cause}` in "data-layout": {$err} errors_target_invalid_alignment = invalid alignment for `{$cause}` in "data-layout": `{$align}` is {$err_kind -> [not_power_of_two] not a power of 2 [too_large] too large *[other] {""} } errors_target_invalid_bits = invalid {$kind} `{$bit}` for `{$cause}` in "data-layout": {$err} errors_target_invalid_bits_size = {$err} errors_target_invalid_datalayout_pointer_spec = unknown pointer specification `{$err}` in datalayout string errors_target_missing_alignment = missing alignment for `{$cause}` in "data-layout" invalid level in `stash_diagnostic`: stashing ItemNoTypeUnderscoreForArrayLengthsEarlySyntaxWarningCallIntoMethodLifetimeIsCharMaybeFruTypoCallAssocMethodAssociatedTypeSuggestionCycleUndeterminedMacroResolutionExprInPatGenericInFieldExprdiagnosticstartend1 warning emitted warnings emitted; For more information about this error, try `rustc --explain `..Some errors have detailed explanations: For more information about an error, try `rustc --explain assertion failed: inner.stashed_diagnostics.is_empty()should only need to collect a backtrace oncemacro_decl_namedef_site_spanDiagnosticspans