EmitIgnoredResolutionErrors in rustdoc::core - Rust (original) (raw)
Struct EmitIgnoredResolutionErrors
struct EmitIgnoredResolutionErrors<'tcx> {
tcx: TyCtxt<'tcx>,
}
Expand description
Due to https://github.com/rust-lang/rust/pull/73566, the name resolution pass may find errors that are never emitted. If typeck is called after this happens, then we’ll get an ICE: ‘Res::Error found but not reported’. To avoid this, emit the errors now.
Override this type to control which nested HIR are visited; seeNestedFilter for details. If you override this type, you must also override maybe_tcx. Read more
If type NestedFilter
is set to visit nested items, this method must also be overridden to provide a map to retrieve nested items.
The result type of the visit_*
methods. Can be either ()
, or ControlFlow<T>
.
Invoked when a nested item is encountered. By default, whenSelf::NestedFilter
is nested_filter::None
, this method does nothing. You probably don’t want to override this method – instead, override Self::NestedFilter or use the “shallow” or “deep” visit patterns described atrustc_hir::intravisit. The only reason to override this method is if you want a nested pattern but cannot supply aTyCtxt
; see maybe_tcx
for advice.
Like visit_nested_item()
, but for trait items. Seevisit_nested_item()
for advice on when to override this method.
Like visit_nested_item()
, but for impl items. Seevisit_nested_item()
for advice on when to override this method.
Like visit_nested_item()
, but for foreign items. Seevisit_nested_item()
for advice on when to override this method.
Invoked to visit the body of a function, method or closure. Likevisit_nested_item
, does nothing by default unless you overrideSelf::NestedFilter
.
Visits the top-level item and (optionally) nested items / impl items. Seevisit_nested_item
for details.
All types are treated as ambiguous types for the purposes of hir visiting in order to ensure that visitors can handle infer vars without it being too error-prone. Read more
All consts are treated as ambiguous consts for the purposes of hir visiting in order to ensure that visitors can handle infer vars without it being too error-prone. Read more
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...)
attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.
Size: 8 bytes