20//! If you do, you must then set the new node's ID to a fresh one.
21//!
22▶//! Spans are used for error messages and for tools to map semantics back to
23//! source code. It is therefore not as important with spans as IDs to be strict
24//! about use (you can't break the compiler by screwing up a span). Obviously, a
· · ·
50use rustc_data_structures::tagged_ptr::TaggedRef;
51use rustc_data_structures::unord::ExtendUnord;
52▶use rustc_errors::codes::*;
53use rustc_errors::{DiagArgFromDisplay, DiagCtxtHandle};
54use rustc_hir::def::{DefKind, LifetimeRes, Namespace, PartialRes, PerNS, Res};
· · ·
53▶use rustc_errors::{DiagArgFromDisplay, DiagCtxtHandle};
54use rustc_hir::def::{DefKind, LifetimeRes, Namespace, PartialRes, PerNS, Res};
55use rustc_hir::def_id::{DefId, LOCAL_CRATE, LocalDefId, LocalDefIdMap};
· · ·
65use rustc_middle::span_bug;
66use rustc_middle::ty::{PerOwnerResolverData, ResolverAstLowering, TyCtxt};
67▶use rustc_session::errors::add_feature_diagnostics;
68use rustc_span::symbol::{Ident, Symbol, kw, sym};
69use rustc_span::{DUMMY_SP, DesugaringKind, Span};
· · ·
245 tcx.features(),
246 tcx.registered_tools(()),
247▶ ShouldEmit::ErrorsAndLints { recovery: Recovery::Allowed },
248 ),
249 delayed_lints: Vec::new(),
+ 17 more matches in this file