Module diagnostics

Re-exports§

use std::fmt; 🔒
use std::fmt::Write; 🔒
use std::num::NonZero; 🔒
use std::sync::Mutex; 🔒
use rustc_abi::Align; 🔒
use rustc_abi::Size; 🔒
use rustc_data_structures::fx::FxBuildHasher; 🔒
use rustc_data_structures::fx::FxHashSet; 🔒
use rustc_errors::Diag; 🔒
use rustc_errors::Level; 🔒
use rustc_errors::MultiSpan; 🔒
use rustc_errors::Sublevel; 🔒
use rustc_span::DUMMY_SP; 🔒
use rustc_span::Span; 🔒
use rustc_span::Symbol; 🔒
use crate::borrow_tracker::stacked_borrows::diagnostics::TagHistory; 🔒
use crate::borrow_tracker::tree_borrows::diagnostics as tree_diagnostics; 🔒
use crate::*; 🔒

RacingOp
SpanDedupDiagnostic: Helps deduplicate a diagnostic to ensure it is only shown once per span.

prune_stacktrace: Attempts to prune a stacktrace to omit the Rust runtime, and returns a bool indicating if any frames were pruned. If the stacktrace does not have any local frames, we conclude that it must be pointing to a problem in the Rust runtime itself, and do not prune it at all.
report_leaks
report_msg 🔒: Report an error or note (depending on the error argument) with the given stacktrace. Also emits a full stacktrace of the interpreter stack. We want to present a multi-line span message for some errors. Diagnostics do not support this directly, so we pass the lines as a Vec<String> and display each line after the first with an additional span_label or note call.
report_result: Report the result of a Miri execution.