Struct charon_lib::errors::ErrorCtx

pub struct ErrorCtx<'ctx> {
    pub continue_on_failure: bool,
    pub error_on_warnings: bool,
    pub dcx: DiagCtxtHandle<'ctx>,
    pub external_decls_with_errors: HashSet<AnyTransId>,
    pub ignored_failed_decls: HashSet<AnyTransId>,
    pub external_dep_sources: HashMap<AnyTransId, HashSet<DepSource>>,
    pub def_id: Option<AnyTransId>,
    pub def_id_is_local: bool,
    pub error_count: usize,
}

The context for tracking and reporting errors.

Fields

continue_on_failure: bool

If true, do not abort on the first error and attempt to extract as much as possible.

error_on_warnings: bool

If true, print the warnings as errors, and abort if any errors were raised.

dcx: DiagCtxtHandle<'ctx>

The compiler session, used for displaying errors.

external_decls_with_errors: HashSet<AnyTransId>

The ids of the external_declarations for which extraction we encountered errors.

ignored_failed_decls: HashSet<AnyTransId>

The ids of the declarations we completely failed to extract and had to ignore.

external_dep_sources: HashMap<AnyTransId, HashSet<DepSource>>

For each external item, a list of locations that point to it. See DepSource.

def_id: Option<AnyTransId>

The id of the definition we are exploring, used to track the source of errors.

def_id_is_local: bool

Whether the definition being explored is local to the crate or not.

error_count: usize

The number of errors encountered so far.

Implementations

impl ErrorCtx<'_>

pub fn continue_on_failure(&self) -> bool

pub(crate) fn has_errors(&self) -> bool

pub(crate) fn span_err_no_register<S: Into<MultiSpan>>( &self, span: S, msg: &str, )

Report an error without registering anything.

pub fn span_err(&mut self, span: Span, msg: &str)

Report and register an error.

pub fn ignore_failed_decl(&mut self, id: AnyTransId)

impl ErrorCtx<'_>

pub fn report_external_deps_errors(&self, f: FmtCtx<'_>)

In case errors happened when extracting the definitions coming from the external dependencies, print a detailed report to explain to the user which dependencies were problematic, and where they are used in the code.