2023-02-10 16:14:18 +00:00
|
|
|
//! This module contains implementations of the `Lift`, `TypeFoldable` and
|
|
|
|
//! `TypeVisitable` traits for various types in the Rust compiler. Most are
|
|
|
|
//! written by hand, though we've recently added some macros and proc-macros
|
|
|
|
//! to help with the tedium.
|
2017-11-11 13:04:36 -05:00
|
|
|
|
2019-05-17 02:20:14 +01:00
|
|
|
use crate::mir::interpret;
|
2023-02-22 02:18:40 +00:00
|
|
|
use crate::ty::fold::{FallibleTypeFolder, TypeFoldable, TypeSuperFoldable};
|
2020-09-02 10:40:56 +03:00
|
|
|
use crate::ty::print::{with_no_trimmed_paths, FmtPrinter, Printer};
|
2023-02-22 02:18:40 +00:00
|
|
|
use crate::ty::visit::{TypeSuperVisitable, TypeVisitable, TypeVisitor};
|
|
|
|
use crate::ty::{self, AliasTy, InferConst, Lift, Term, TermKind, Ty, TyCtxt};
|
2020-01-05 02:37:57 +01:00
|
|
|
use rustc_hir::def::Namespace;
|
2023-04-19 10:57:17 +00:00
|
|
|
use rustc_index::{Idx, IndexVec};
|
2023-01-22 17:06:28 -05:00
|
|
|
use rustc_target::abi::TyAndLayout;
|
2023-07-06 10:17:26 +01:00
|
|
|
use rustc_type_ir::{ConstKind, DebugWithInfcx, InferCtxtLike, OptWithInfcx};
|
2015-09-06 21:51:58 +03:00
|
|
|
|
2023-07-06 10:17:26 +01:00
|
|
|
use std::fmt::{self, Debug};
|
2020-10-21 14:22:44 +02:00
|
|
|
use std::ops::ControlFlow;
|
2015-09-06 21:51:58 +03:00
|
|
|
use std::rc::Rc;
|
2019-06-18 08:15:27 -04:00
|
|
|
use std::sync::Arc;
|
2015-09-06 21:51:58 +03:00
|
|
|
|
2023-09-16 08:36:28 +02:00
|
|
|
use super::print::PrettyPrinter;
|
2023-07-06 10:17:26 +01:00
|
|
|
use super::{GenericArg, GenericArgKind, Region};
|
|
|
|
|
2019-01-19 06:33:44 +02:00
|
|
|
impl fmt::Debug for ty::TraitDef {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2019-01-25 12:11:50 +02:00
|
|
|
ty::tls::with(|tcx| {
|
2022-02-18 16:15:29 -05:00
|
|
|
with_no_trimmed_paths!({
|
|
|
|
f.write_str(
|
|
|
|
&FmtPrinter::new(tcx, Namespace::TypeNS)
|
|
|
|
.print_def_path(self.def_id, &[])?
|
|
|
|
.into_buffer(),
|
|
|
|
)
|
|
|
|
})
|
2019-01-19 06:33:44 +02:00
|
|
|
})
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-03-05 07:28:41 +11:00
|
|
|
impl<'tcx> fmt::Debug for ty::AdtDef<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2019-01-25 12:11:50 +02:00
|
|
|
ty::tls::with(|tcx| {
|
2022-02-18 16:15:29 -05:00
|
|
|
with_no_trimmed_paths!({
|
|
|
|
f.write_str(
|
|
|
|
&FmtPrinter::new(tcx, Namespace::TypeNS)
|
2022-03-05 07:28:41 +11:00
|
|
|
.print_def_path(self.did(), &[])?
|
2022-02-18 16:15:29 -05:00
|
|
|
.into_buffer(),
|
|
|
|
)
|
|
|
|
})
|
2019-01-19 06:33:44 +02:00
|
|
|
})
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl fmt::Debug for ty::UpvarId {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2019-06-19 15:44:51 +02:00
|
|
|
let name = ty::tls::with(|tcx| tcx.hir().name(self.var_path.hir_id));
|
2019-01-19 06:33:44 +02:00
|
|
|
write!(f, "UpvarId({:?};`{}`;{:?})", self.var_path.hir_id, name, self.closure_expr_id)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::ExistentialTraitRef<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2022-02-16 13:04:48 -05:00
|
|
|
with_no_trimmed_paths!(fmt::Display::fmt(self, f))
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::adjustment::Adjustment<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
write!(f, "{:?} -> {}", self.kind, self.target)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-12-18 13:24:55 -05:00
|
|
|
impl fmt::Debug for ty::BoundRegionKind {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
match *self {
|
2023-04-06 22:07:21 -04:00
|
|
|
ty::BrAnon(span) => write!(f, "BrAnon({span:?})"),
|
2019-01-19 06:33:44 +02:00
|
|
|
ty::BrNamed(did, name) => {
|
2022-04-15 19:27:53 +02:00
|
|
|
if did.is_crate_root() {
|
2023-07-25 22:00:13 +02:00
|
|
|
write!(f, "BrNamed({name})")
|
2019-11-30 17:29:56 +02:00
|
|
|
} else {
|
2023-07-25 22:00:13 +02:00
|
|
|
write!(f, "BrNamed({did:?}, {name})")
|
2019-11-30 17:29:56 +02:00
|
|
|
}
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
ty::BrEnv => write!(f, "BrEnv"),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl fmt::Debug for ty::FreeRegion {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
write!(f, "ReFree({:?}, {:?})", self.scope, self.bound_region)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::FnSig<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2023-07-06 10:17:26 +01:00
|
|
|
OptWithInfcx::new_no_ctx(self).fmt(f)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for ty::FnSig<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
let sig = this.data;
|
|
|
|
let ty::FnSig { inputs_and_output: _, c_variadic, unsafety, abi } = sig;
|
2023-05-26 18:54:59 +01:00
|
|
|
|
|
|
|
write!(f, "{}", unsafety.prefix_str())?;
|
|
|
|
match abi {
|
|
|
|
rustc_target::spec::abi::Abi::Rust => (),
|
|
|
|
abi => write!(f, "extern \"{abi:?}\" ")?,
|
|
|
|
};
|
|
|
|
|
|
|
|
write!(f, "fn(")?;
|
2023-07-06 10:17:26 +01:00
|
|
|
let inputs = sig.inputs();
|
2023-05-26 18:54:59 +01:00
|
|
|
match inputs.len() {
|
|
|
|
0 if *c_variadic => write!(f, "...)")?,
|
|
|
|
0 => write!(f, ")")?,
|
|
|
|
_ => {
|
2023-07-06 10:17:26 +01:00
|
|
|
for ty in &sig.inputs()[0..(sig.inputs().len() - 1)] {
|
|
|
|
write!(f, "{:?}, ", &this.wrap(ty))?;
|
2023-05-26 18:54:59 +01:00
|
|
|
}
|
2023-07-06 10:17:26 +01:00
|
|
|
write!(f, "{:?}", &this.wrap(sig.inputs().last().unwrap()))?;
|
2023-05-26 18:54:59 +01:00
|
|
|
if *c_variadic {
|
|
|
|
write!(f, "...")?;
|
|
|
|
}
|
|
|
|
write!(f, ")")?;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-07-06 10:17:26 +01:00
|
|
|
match sig.output().kind() {
|
2023-05-26 18:54:59 +01:00
|
|
|
ty::Tuple(list) if list.is_empty() => Ok(()),
|
2023-07-06 10:17:26 +01:00
|
|
|
_ => write!(f, " -> {:?}", &this.wrap(sig.output())),
|
2023-05-26 18:54:59 +01:00
|
|
|
}
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx> fmt::Debug for ty::ConstVid<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2023-04-22 00:08:38 +00:00
|
|
|
write!(f, "?{}c", self.index)
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-09-10 05:11:37 +00:00
|
|
|
impl fmt::Debug for ty::EffectVid<'_> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
write!(f, "?{}e", self.index)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::TraitRef<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2022-02-16 13:04:48 -05:00
|
|
|
with_no_trimmed_paths!(fmt::Display::fmt(self, f))
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-07-06 10:17:26 +01:00
|
|
|
impl<'tcx> ty::DebugWithInfcx<TyCtxt<'tcx>> for Ty<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
this.data.fmt(f)
|
|
|
|
}
|
|
|
|
}
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for Ty<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2023-09-07 15:14:40 +10:00
|
|
|
with_no_trimmed_paths!(fmt::Debug::fmt(self.kind(), f))
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl fmt::Debug for ty::ParamTy {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2019-05-06 13:12:04 +01:00
|
|
|
write!(f, "{}/#{}", self.name, self.index)
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl fmt::Debug for ty::ParamConst {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
write!(f, "{}/#{}", self.name, self.index)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::TraitPredicate<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2023-07-29 08:20:25 +00:00
|
|
|
// FIXME(effects) printing?
|
2021-10-11 18:10:35 -03:00
|
|
|
write!(f, "TraitPredicate({:?}, polarity:{:?})", self.trait_ref, self.polarity)
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::ProjectionPredicate<'tcx> {
|
2019-01-19 06:33:44 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2022-01-08 09:28:12 +00:00
|
|
|
write!(f, "ProjectionPredicate({:?}, {:?})", self.projection_ty, self.term)
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::Predicate<'tcx> {
|
2020-05-11 22:06:41 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2021-01-07 11:20:28 -05:00
|
|
|
write!(f, "{:?}", self.kind())
|
2020-05-11 22:06:41 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-06-16 06:27:41 +00:00
|
|
|
impl<'tcx> fmt::Debug for ty::Clause<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
write!(f, "{:?}", self.kind())
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-06-16 05:59:42 +00:00
|
|
|
impl<'tcx> fmt::Debug for ty::ClauseKind<'tcx> {
|
2022-11-24 18:14:58 -03:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
match *self {
|
2023-06-16 05:59:42 +00:00
|
|
|
ty::ClauseKind::ConstArgHasType(ct, ty) => write!(f, "ConstArgHasType({ct:?}, {ty:?})"),
|
|
|
|
ty::ClauseKind::Trait(ref a) => a.fmt(f),
|
|
|
|
ty::ClauseKind::RegionOutlives(ref pair) => pair.fmt(f),
|
|
|
|
ty::ClauseKind::TypeOutlives(ref pair) => pair.fmt(f),
|
|
|
|
ty::ClauseKind::Projection(ref pair) => pair.fmt(f),
|
2023-07-25 22:00:13 +02:00
|
|
|
ty::ClauseKind::WellFormed(ref data) => write!(f, "WellFormed({data:?})"),
|
2023-06-16 05:59:42 +00:00
|
|
|
ty::ClauseKind::ConstEvaluatable(ct) => {
|
2023-06-15 18:35:52 +00:00
|
|
|
write!(f, "ConstEvaluatable({ct:?})")
|
|
|
|
}
|
2022-11-24 18:14:58 -03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-12-15 19:32:30 -05:00
|
|
|
impl<'tcx> fmt::Debug for ty::PredicateKind<'tcx> {
|
2020-07-09 00:35:55 +02:00
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
match *self {
|
2022-11-24 18:14:58 -03:00
|
|
|
ty::PredicateKind::Clause(ref a) => a.fmt(f),
|
2021-01-07 11:20:28 -05:00
|
|
|
ty::PredicateKind::Subtype(ref pair) => pair.fmt(f),
|
2020-11-21 07:06:16 -05:00
|
|
|
ty::PredicateKind::Coerce(ref pair) => pair.fmt(f),
|
2021-01-07 11:20:28 -05:00
|
|
|
ty::PredicateKind::ObjectSafe(trait_def_id) => {
|
2023-07-25 22:00:13 +02:00
|
|
|
write!(f, "ObjectSafe({trait_def_id:?})")
|
2020-05-11 21:09:57 +02:00
|
|
|
}
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::PredicateKind::ClosureKind(closure_def_id, closure_args, kind) => {
|
2023-07-25 22:00:13 +02:00
|
|
|
write!(f, "ClosureKind({closure_def_id:?}, {closure_args:?}, {kind:?})")
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
2023-07-25 22:00:13 +02:00
|
|
|
ty::PredicateKind::ConstEquate(c1, c2) => write!(f, "ConstEquate({c1:?}, {c2:?})"),
|
2022-11-02 15:10:05 +00:00
|
|
|
ty::PredicateKind::Ambiguous => write!(f, "Ambiguous"),
|
2023-03-21 22:20:54 +00:00
|
|
|
ty::PredicateKind::AliasRelate(t1, t2, dir) => {
|
|
|
|
write!(f, "AliasRelate({t1:?}, {dir:?}, {t2:?})")
|
|
|
|
}
|
2019-01-19 06:33:44 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-01-17 14:06:12 +01:00
|
|
|
impl<'tcx> fmt::Debug for AliasTy<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2023-07-06 10:17:26 +01:00
|
|
|
OptWithInfcx::new_no_ctx(self).fmt(f)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for AliasTy<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
2023-01-17 14:06:12 +01:00
|
|
|
f.debug_struct("AliasTy")
|
2023-07-11 22:35:29 +01:00
|
|
|
.field("args", &this.map(|data| data.args))
|
2023-07-06 10:17:26 +01:00
|
|
|
.field("def_id", &this.data.def_id)
|
2023-01-17 14:06:12 +01:00
|
|
|
.finish()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-05-16 04:25:25 +01:00
|
|
|
impl<'tcx> fmt::Debug for ty::InferConst<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
match self {
|
|
|
|
InferConst::Var(var) => write!(f, "{var:?}"),
|
2023-09-10 05:11:37 +00:00
|
|
|
InferConst::EffectVar(var) => write!(f, "{var:?}"),
|
2023-05-16 04:25:25 +01:00
|
|
|
InferConst::Fresh(var) => write!(f, "Fresh({var:?})"),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2023-07-06 10:17:26 +01:00
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for ty::InferConst<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
use ty::InferConst::*;
|
|
|
|
match this.infcx.and_then(|infcx| infcx.universe_of_ct(*this.data)) {
|
|
|
|
None => write!(f, "{:?}", this.data),
|
|
|
|
Some(universe) => match *this.data {
|
|
|
|
Var(vid) => write!(f, "?{}_{}c", vid.index, universe.index()),
|
2023-09-10 05:11:37 +00:00
|
|
|
EffectVar(vid) => write!(f, "?{}_{}e", vid.index, universe.index()),
|
2023-07-06 10:17:26 +01:00
|
|
|
Fresh(_) => {
|
|
|
|
unreachable!()
|
|
|
|
}
|
|
|
|
},
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx> fmt::Debug for ty::consts::Expr<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
OptWithInfcx::new_no_ctx(self).fmt(f)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for ty::consts::Expr<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
match this.data {
|
|
|
|
ty::Expr::Binop(op, lhs, rhs) => {
|
|
|
|
write!(f, "({op:?}: {:?}, {:?})", &this.wrap(lhs), &this.wrap(rhs))
|
|
|
|
}
|
|
|
|
ty::Expr::UnOp(op, rhs) => write!(f, "({op:?}: {:?})", &this.wrap(rhs)),
|
|
|
|
ty::Expr::FunctionCall(func, args) => {
|
|
|
|
write!(f, "{:?}(", &this.wrap(func))?;
|
|
|
|
for arg in args.as_slice().iter().rev().skip(1).rev() {
|
|
|
|
write!(f, "{:?}, ", &this.wrap(arg))?;
|
|
|
|
}
|
|
|
|
if let Some(arg) = args.last() {
|
|
|
|
write!(f, "{:?}", &this.wrap(arg))?;
|
|
|
|
}
|
|
|
|
|
|
|
|
write!(f, ")")
|
|
|
|
}
|
|
|
|
ty::Expr::Cast(cast_kind, lhs, rhs) => {
|
|
|
|
write!(f, "({cast_kind:?}: {:?}, {:?})", &this.wrap(lhs), &this.wrap(rhs))
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx> fmt::Debug for ty::UnevaluatedConst<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
OptWithInfcx::new_no_ctx(self).fmt(f)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for ty::UnevaluatedConst<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
f.debug_struct("UnevaluatedConst")
|
|
|
|
.field("def", &this.data.def)
|
2023-07-11 22:35:29 +01:00
|
|
|
.field("args", &this.wrap(this.data.args))
|
2023-07-06 10:17:26 +01:00
|
|
|
.finish()
|
|
|
|
}
|
|
|
|
}
|
2023-05-16 04:25:25 +01:00
|
|
|
|
|
|
|
impl<'tcx> fmt::Debug for ty::Const<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
2023-07-06 10:17:26 +01:00
|
|
|
OptWithInfcx::new_no_ctx(self).fmt(f)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for ty::Const<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
2023-09-16 08:36:28 +02:00
|
|
|
// If this is a value, we spend some effort to make it look nice.
|
|
|
|
if let ConstKind::Value(_) = this.data.kind() {
|
|
|
|
return ty::tls::with(move |tcx| {
|
|
|
|
// Somehow trying to lift the valtree results in lifetime errors, so we lift the
|
|
|
|
// entire constant.
|
|
|
|
let lifted = tcx.lift(*this.data).unwrap();
|
|
|
|
let ConstKind::Value(valtree) = lifted.kind() else {
|
|
|
|
bug!("we checked that this is a valtree")
|
|
|
|
};
|
|
|
|
let cx = FmtPrinter::new(tcx, Namespace::ValueNS);
|
|
|
|
let cx =
|
|
|
|
cx.pretty_print_const_valtree(valtree, lifted.ty(), /*print_ty*/ true)?;
|
|
|
|
f.write_str(&cx.into_buffer())
|
|
|
|
});
|
|
|
|
}
|
|
|
|
// Fall back to something verbose.
|
2023-07-06 10:17:26 +01:00
|
|
|
write!(
|
|
|
|
f,
|
2023-09-16 08:36:28 +02:00
|
|
|
"{kind:?}: {ty:?}",
|
|
|
|
ty = &this.map(|data| data.ty()),
|
|
|
|
kind = &this.map(|data| data.kind())
|
2023-07-06 10:17:26 +01:00
|
|
|
)
|
2023-05-16 04:25:25 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-05-26 18:54:59 +01:00
|
|
|
impl fmt::Debug for ty::BoundTy {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
match self.kind {
|
|
|
|
ty::BoundTyKind::Anon => write!(f, "{:?}", self.var),
|
|
|
|
ty::BoundTyKind::Param(_, sym) => write!(f, "{sym:?}"),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<T: fmt::Debug> fmt::Debug for ty::Placeholder<T> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
if self.universe == ty::UniverseIndex::ROOT {
|
|
|
|
write!(f, "!{:?}", self.bound)
|
|
|
|
} else {
|
|
|
|
write!(f, "!{}_{:?}", self.universe.index(), self.bound)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-07-06 10:17:26 +01:00
|
|
|
impl<'tcx> fmt::Debug for GenericArg<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
match self.unpack() {
|
|
|
|
GenericArgKind::Lifetime(lt) => lt.fmt(f),
|
|
|
|
GenericArgKind::Type(ty) => ty.fmt(f),
|
|
|
|
GenericArgKind::Const(ct) => ct.fmt(f),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for GenericArg<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
match this.data.unpack() {
|
|
|
|
GenericArgKind::Lifetime(lt) => write!(f, "{:?}", &this.wrap(lt)),
|
|
|
|
GenericArgKind::Const(ct) => write!(f, "{:?}", &this.wrap(ct)),
|
|
|
|
GenericArgKind::Type(ty) => write!(f, "{:?}", &this.wrap(ty)),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx> fmt::Debug for Region<'tcx> {
|
|
|
|
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
|
|
write!(f, "{:?}", self.kind())
|
|
|
|
}
|
|
|
|
}
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for Region<'tcx> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
write!(f, "{:?}", &this.map(|data| data.kind()))
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx> DebugWithInfcx<TyCtxt<'tcx>> for ty::RegionVid {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
match this.infcx.and_then(|infcx| infcx.universe_of_lt(*this.data)) {
|
|
|
|
Some(universe) => write!(f, "'?{}_{}", this.data.index(), universe.index()),
|
|
|
|
None => write!(f, "{:?}", this.data),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx, T: DebugWithInfcx<TyCtxt<'tcx>>> DebugWithInfcx<TyCtxt<'tcx>> for ty::Binder<'tcx, T> {
|
|
|
|
fn fmt<InfCtx: InferCtxtLike<TyCtxt<'tcx>>>(
|
|
|
|
this: OptWithInfcx<'_, TyCtxt<'tcx>, InfCtx, &Self>,
|
|
|
|
f: &mut core::fmt::Formatter<'_>,
|
|
|
|
) -> core::fmt::Result {
|
|
|
|
f.debug_tuple("Binder")
|
|
|
|
.field(&this.map(|data| data.as_ref().skip_binder()))
|
|
|
|
.field(&this.data.bound_vars())
|
|
|
|
.finish()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-11-11 13:04:36 -05:00
|
|
|
///////////////////////////////////////////////////////////////////////////
|
|
|
|
// Atomic structs
|
|
|
|
//
|
|
|
|
// For things that don't carry any arena-allocated data (and are
|
2023-04-09 17:35:02 -04:00
|
|
|
// copy...), just add them to one of these lists as appropriate.
|
2017-11-11 13:04:36 -05:00
|
|
|
|
2023-02-10 16:14:18 +00:00
|
|
|
// For things for which the type library provides traversal implementations
|
|
|
|
// for all Interners, we only need to provide a Lift implementation:
|
|
|
|
CloneLiftImpls! {
|
2017-11-11 13:04:36 -05:00
|
|
|
(),
|
2018-02-09 10:34:23 -05:00
|
|
|
bool,
|
|
|
|
usize,
|
2022-09-11 14:42:43 +02:00
|
|
|
u16,
|
2020-08-15 04:42:13 -07:00
|
|
|
u32,
|
2018-02-09 10:34:23 -05:00
|
|
|
u64,
|
2018-11-26 17:30:19 +01:00
|
|
|
String,
|
2023-02-10 16:14:18 +00:00
|
|
|
rustc_type_ir::DebruijnIndex,
|
|
|
|
}
|
|
|
|
|
|
|
|
// For things about which the type library does not know, or does not
|
|
|
|
// provide any traversal implementations, we need to provide both a Lift
|
|
|
|
// implementation and traversal implementations (the latter only for
|
|
|
|
// TyCtxt<'_> interners).
|
|
|
|
TrivialTypeTraversalAndLiftImpls! {
|
2023-03-28 12:32:57 -07:00
|
|
|
::rustc_target::abi::FieldIdx,
|
2023-02-10 16:14:18 +00:00
|
|
|
::rustc_target::abi::VariantIdx,
|
2019-02-05 11:20:45 -06:00
|
|
|
crate::middle::region::Scope,
|
2020-12-12 15:25:55 +01:00
|
|
|
crate::ty::FloatTy,
|
2020-04-27 23:26:11 +05:30
|
|
|
::rustc_ast::InlineAsmOptions,
|
|
|
|
::rustc_ast::InlineAsmTemplatePiece,
|
|
|
|
::rustc_ast::NodeId,
|
2019-12-31 20:15:40 +03:00
|
|
|
::rustc_span::symbol::Symbol,
|
2020-01-05 02:37:57 +01:00
|
|
|
::rustc_hir::def::Res,
|
|
|
|
::rustc_hir::def_id::DefId,
|
2020-07-08 01:03:19 +02:00
|
|
|
::rustc_hir::def_id::LocalDefId,
|
2020-08-02 15:42:08 +02:00
|
|
|
::rustc_hir::HirId,
|
2020-01-05 02:37:57 +01:00
|
|
|
::rustc_hir::MatchSource,
|
|
|
|
::rustc_hir::Mutability,
|
|
|
|
::rustc_hir::Unsafety,
|
2020-02-14 18:17:50 +00:00
|
|
|
::rustc_target::asm::InlineAsmRegOrRegClass,
|
2018-04-25 19:30:39 +03:00
|
|
|
::rustc_target::spec::abi::Abi,
|
2023-06-29 12:36:19 +10:00
|
|
|
crate::mir::coverage::CounterId,
|
2023-06-29 12:14:04 +10:00
|
|
|
crate::mir::coverage::ExpressionId,
|
2020-08-15 04:42:13 -07:00
|
|
|
crate::mir::coverage::MappedExpressionIndex,
|
2019-02-05 11:20:45 -06:00
|
|
|
crate::mir::Local,
|
|
|
|
crate::mir::Promoted,
|
|
|
|
crate::traits::Reveal,
|
|
|
|
crate::ty::adjustment::AutoBorrowMutability,
|
|
|
|
crate::ty::AdtKind,
|
2021-08-27 05:02:23 +00:00
|
|
|
crate::ty::BoundConstness,
|
2020-12-18 13:24:55 -05:00
|
|
|
// Including `BoundRegionKind` is a *bit* dubious, but direct
|
2018-02-09 10:34:23 -05:00
|
|
|
// references to bound region appear in `ty::Error`, and aren't
|
|
|
|
// really meant to be folded. In general, we can only fold a fully
|
|
|
|
// general `Region`.
|
2020-12-18 13:24:55 -05:00
|
|
|
crate::ty::BoundRegionKind,
|
2020-08-02 15:42:08 +02:00
|
|
|
crate::ty::AssocItem,
|
2022-07-24 19:33:26 +00:00
|
|
|
crate::ty::AssocKind,
|
2023-01-13 23:53:28 +00:00
|
|
|
crate::ty::AliasKind,
|
2023-03-21 21:50:16 +00:00
|
|
|
crate::ty::AliasRelationDirection,
|
2023-04-06 21:12:17 -04:00
|
|
|
crate::ty::Placeholder<crate::ty::BoundRegion>,
|
|
|
|
crate::ty::Placeholder<crate::ty::BoundTy>,
|
2023-05-26 18:54:59 +01:00
|
|
|
crate::ty::Placeholder<ty::BoundVar>,
|
2019-02-05 11:20:45 -06:00
|
|
|
crate::ty::ClosureKind,
|
2018-12-07 17:40:23 +02:00
|
|
|
crate::ty::FreeRegion,
|
|
|
|
crate::ty::InferTy,
|
2019-02-05 11:20:45 -06:00
|
|
|
crate::ty::IntVarValue,
|
2019-02-20 01:18:43 +00:00
|
|
|
crate::ty::ParamConst,
|
2019-02-05 11:20:45 -06:00
|
|
|
crate::ty::ParamTy,
|
2023-07-05 20:07:03 +02:00
|
|
|
crate::ty::adjustment::PointerCoercion,
|
2018-12-10 17:36:24 +02:00
|
|
|
crate::ty::RegionVid,
|
2019-02-05 11:20:45 -06:00
|
|
|
crate::ty::UniverseIndex,
|
|
|
|
crate::ty::Variance,
|
2019-12-31 20:15:40 +03:00
|
|
|
::rustc_span::Span,
|
2022-10-25 17:59:18 +00:00
|
|
|
::rustc_span::symbol::Ident,
|
2022-01-23 12:34:26 -06:00
|
|
|
::rustc_errors::ErrorGuaranteed,
|
2022-09-08 09:04:52 +00:00
|
|
|
interpret::Scalar,
|
2023-09-11 20:01:48 +02:00
|
|
|
interpret::AllocId,
|
2022-09-08 09:04:52 +00:00
|
|
|
rustc_target::abi::Size,
|
2022-09-15 15:05:03 +00:00
|
|
|
ty::BoundVar,
|
|
|
|
}
|
|
|
|
|
|
|
|
TrivialTypeTraversalAndLiftImpls! {
|
2023-04-16 14:01:43 +10:00
|
|
|
ty::ValTree<'tcx>,
|
2017-11-11 13:04:36 -05:00
|
|
|
}
|
|
|
|
|
2015-09-06 21:51:58 +03:00
|
|
|
///////////////////////////////////////////////////////////////////////////
|
|
|
|
// Lift implementations
|
|
|
|
|
|
|
|
impl<'tcx, A: Lift<'tcx>, B: Lift<'tcx>> Lift<'tcx> for (A, B) {
|
|
|
|
type Lifted = (A::Lifted, B::Lifted);
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2020-10-21 23:52:41 +02:00
|
|
|
Some((tcx.lift(self.0)?, tcx.lift(self.1)?))
|
2015-09-06 21:51:58 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-12-26 14:34:03 +01:00
|
|
|
impl<'tcx, A: Lift<'tcx>, B: Lift<'tcx>, C: Lift<'tcx>> Lift<'tcx> for (A, B, C) {
|
|
|
|
type Lifted = (A::Lifted, B::Lifted, C::Lifted);
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2020-10-21 23:52:41 +02:00
|
|
|
Some((tcx.lift(self.0)?, tcx.lift(self.1)?, tcx.lift(self.2)?))
|
2019-06-18 08:52:23 -04:00
|
|
|
}
|
2016-12-26 14:34:03 +01:00
|
|
|
}
|
|
|
|
|
2016-04-29 06:00:23 +03:00
|
|
|
impl<'tcx, T: Lift<'tcx>> Lift<'tcx> for Option<T> {
|
|
|
|
type Lifted = Option<T::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2022-09-21 08:29:19 +00:00
|
|
|
Some(match self {
|
|
|
|
Some(x) => Some(tcx.lift(x)?),
|
|
|
|
None => None,
|
|
|
|
})
|
2016-04-29 06:00:23 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl<'tcx, T: Lift<'tcx>, E: Lift<'tcx>> Lift<'tcx> for Result<T, E> {
|
|
|
|
type Lifted = Result<T::Lifted, E::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
|
|
|
match self {
|
|
|
|
Ok(x) => tcx.lift(x).map(Ok),
|
|
|
|
Err(e) => tcx.lift(e).map(Err),
|
2016-04-29 06:00:23 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-08-07 08:08:53 +03:00
|
|
|
impl<'tcx, T: Lift<'tcx>> Lift<'tcx> for Box<T> {
|
|
|
|
type Lifted = Box<T::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2022-09-15 13:37:34 +00:00
|
|
|
Some(Box::new(tcx.lift(*self)?))
|
2017-08-07 08:08:53 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-10-16 21:59:49 +02:00
|
|
|
impl<'tcx, T: Lift<'tcx> + Clone> Lift<'tcx> for Rc<T> {
|
2019-06-05 05:58:08 -04:00
|
|
|
type Lifted = Rc<T::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2022-09-15 13:37:34 +00:00
|
|
|
Some(Rc::new(tcx.lift(self.as_ref().clone())?))
|
2019-06-05 05:58:08 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-10-16 21:59:49 +02:00
|
|
|
impl<'tcx, T: Lift<'tcx> + Clone> Lift<'tcx> for Arc<T> {
|
2019-06-18 08:15:27 -04:00
|
|
|
type Lifted = Arc<T::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2022-09-15 13:37:34 +00:00
|
|
|
Some(Arc::new(tcx.lift(self.as_ref().clone())?))
|
2015-09-06 21:51:58 +03:00
|
|
|
}
|
|
|
|
}
|
2016-05-02 18:07:47 +03:00
|
|
|
impl<'tcx, T: Lift<'tcx>> Lift<'tcx> for Vec<T> {
|
|
|
|
type Lifted = Vec<T::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
|
|
|
self.into_iter().map(|v| tcx.lift(v)).collect()
|
2016-05-02 18:07:47 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-11-11 13:04:36 -05:00
|
|
|
impl<'tcx, I: Idx, T: Lift<'tcx>> Lift<'tcx> for IndexVec<I, T> {
|
|
|
|
type Lifted = IndexVec<I, T::Lifted>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
|
|
|
self.into_iter().map(|e| tcx.lift(e)).collect()
|
2017-11-11 13:04:36 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-01-08 09:28:12 +00:00
|
|
|
impl<'a, 'tcx> Lift<'tcx> for Term<'a> {
|
|
|
|
type Lifted = ty::Term<'tcx>;
|
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
2022-09-05 14:03:53 +10:00
|
|
|
Some(
|
|
|
|
match self.unpack() {
|
|
|
|
TermKind::Ty(ty) => TermKind::Ty(tcx.lift(ty)?),
|
|
|
|
TermKind::Const(c) => TermKind::Const(tcx.lift(c)?),
|
|
|
|
}
|
|
|
|
.pack(),
|
|
|
|
)
|
2022-01-08 09:28:12 +00:00
|
|
|
}
|
|
|
|
}
|
2017-08-07 08:08:53 +03:00
|
|
|
impl<'a, 'tcx> Lift<'tcx> for ty::ParamEnv<'a> {
|
|
|
|
type Lifted = ty::ParamEnv<'tcx>;
|
2020-10-16 21:59:49 +02:00
|
|
|
fn lift_to_tcx(self, tcx: TyCtxt<'tcx>) -> Option<Self::Lifted> {
|
|
|
|
tcx.lift(self.caller_bounds())
|
2023-07-27 15:50:42 +00:00
|
|
|
.map(|caller_bounds| ty::ParamEnv::new(caller_bounds, self.reveal()))
|
2017-08-07 08:08:53 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-09-06 21:51:58 +03:00
|
|
|
///////////////////////////////////////////////////////////////////////////
|
2023-02-10 16:14:18 +00:00
|
|
|
// Traversal implementations.
|
2015-09-06 21:51:58 +03:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for ty::AdtDef<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
_visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
2023-01-17 23:17:13 -08:00
|
|
|
ControlFlow::Continue(())
|
2018-02-09 10:34:23 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx, T: TypeFoldable<TyCtxt<'tcx>>> TypeFoldable<TyCtxt<'tcx>> for ty::Binder<'tcx, T> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2021-12-01 00:55:57 +00:00
|
|
|
folder.try_fold_binder(self)
|
2016-01-06 02:01:28 +00:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2016-01-06 02:01:28 +00:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx, T: TypeVisitable<TyCtxt<'tcx>>> TypeVisitable<TyCtxt<'tcx>> for ty::Binder<'tcx, T> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
2016-01-08 23:34:05 +00:00
|
|
|
visitor.visit_binder(self)
|
2015-11-18 09:38:57 +00:00
|
|
|
}
|
2015-09-06 21:51:58 +03:00
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx, T: TypeFoldable<TyCtxt<'tcx>>> TypeSuperFoldable<TyCtxt<'tcx>> for ty::Binder<'tcx, T> {
|
|
|
|
fn try_super_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
2021-12-01 00:55:57 +00:00
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
self.try_map_bound(|ty| ty.try_fold_with(folder))
|
2015-11-18 09:38:57 +00:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2015-11-18 09:38:57 +00:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx, T: TypeVisitable<TyCtxt<'tcx>>> TypeSuperVisitable<TyCtxt<'tcx>>
|
|
|
|
for ty::Binder<'tcx, T>
|
|
|
|
{
|
|
|
|
fn super_visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
self.as_ref().skip_binder().visit_with(visitor)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for &'tcx ty::List<ty::PolyExistentialPredicate<'tcx>> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2023-02-17 14:33:08 +11:00
|
|
|
ty::util::fold_list(self, folder, |tcx, v| tcx.mk_poly_existential_predicates(v))
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for &'tcx ty::List<ty::Const<'tcx>> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2023-02-17 14:33:08 +11:00
|
|
|
ty::util::fold_list(self, folder, |tcx, v| tcx.mk_const_list(v))
|
2022-07-27 07:27:52 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for Ty<'tcx> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
folder.try_fold_ty(self)
|
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for Ty<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
visitor.visit_ty(*self)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-11 09:13:27 +00:00
|
|
|
impl<'tcx> TypeSuperFoldable<TyCtxt<'tcx>> for Ty<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn try_super_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
2021-12-01 00:55:57 +00:00
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2020-10-24 09:27:15 +02:00
|
|
|
let kind = match *self.kind() {
|
2021-12-01 00:55:57 +00:00
|
|
|
ty::RawPtr(tm) => ty::RawPtr(tm.try_fold_with(folder)?),
|
|
|
|
ty::Array(typ, sz) => ty::Array(typ.try_fold_with(folder)?, sz.try_fold_with(folder)?),
|
|
|
|
ty::Slice(typ) => ty::Slice(typ.try_fold_with(folder)?),
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::Adt(tid, args) => ty::Adt(tid, args.try_fold_with(folder)?),
|
2022-04-13 16:11:28 -07:00
|
|
|
ty::Dynamic(trait_ty, region, representation) => ty::Dynamic(
|
|
|
|
trait_ty.try_fold_with(folder)?,
|
|
|
|
region.try_fold_with(folder)?,
|
|
|
|
representation,
|
|
|
|
),
|
2021-12-01 00:55:57 +00:00
|
|
|
ty::Tuple(ts) => ty::Tuple(ts.try_fold_with(folder)?),
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::FnDef(def_id, args) => ty::FnDef(def_id, args.try_fold_with(folder)?),
|
2021-12-01 00:55:57 +00:00
|
|
|
ty::FnPtr(f) => ty::FnPtr(f.try_fold_with(folder)?),
|
|
|
|
ty::Ref(r, ty, mutbl) => {
|
|
|
|
ty::Ref(r.try_fold_with(folder)?, ty.try_fold_with(folder)?, mutbl)
|
2015-06-13 13:15:03 -07:00
|
|
|
}
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::Generator(did, args, movability) => {
|
|
|
|
ty::Generator(did, args.try_fold_with(folder)?, movability)
|
2017-07-05 14:57:26 -07:00
|
|
|
}
|
2021-12-01 00:55:57 +00:00
|
|
|
ty::GeneratorWitness(types) => ty::GeneratorWitness(types.try_fold_with(folder)?),
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::GeneratorWitnessMIR(did, args) => {
|
|
|
|
ty::GeneratorWitnessMIR(did, args.try_fold_with(folder)?)
|
2022-10-01 14:56:24 +02:00
|
|
|
}
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::Closure(did, args) => ty::Closure(did, args.try_fold_with(folder)?),
|
2022-11-27 17:52:17 +00:00
|
|
|
ty::Alias(kind, data) => ty::Alias(kind, data.try_fold_with(folder)?),
|
2018-10-22 20:37:56 +02:00
|
|
|
|
|
|
|
ty::Bool
|
|
|
|
| ty::Char
|
|
|
|
| ty::Str
|
|
|
|
| ty::Int(_)
|
|
|
|
| ty::Uint(_)
|
|
|
|
| ty::Float(_)
|
2020-05-05 23:02:09 -05:00
|
|
|
| ty::Error(_)
|
2018-10-22 20:37:56 +02:00
|
|
|
| ty::Infer(_)
|
|
|
|
| ty::Param(..)
|
|
|
|
| ty::Bound(..)
|
2018-11-02 18:48:24 +01:00
|
|
|
| ty::Placeholder(..)
|
2018-10-22 20:37:56 +02:00
|
|
|
| ty::Never
|
2021-05-19 13:34:54 +02:00
|
|
|
| ty::Foreign(..) => return Ok(self),
|
2015-11-18 09:38:57 +00:00
|
|
|
};
|
2016-11-24 21:10:08 +11:00
|
|
|
|
2023-02-20 10:19:09 +11:00
|
|
|
Ok(if *self.kind() == kind { self } else { folder.interner().mk_ty_from_kind(kind) })
|
2015-11-18 09:38:57 +00:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2015-11-18 09:38:57 +00:00
|
|
|
|
2023-02-09 19:38:07 +00:00
|
|
|
impl<'tcx> TypeSuperVisitable<TyCtxt<'tcx>> for Ty<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn super_visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
2020-08-03 00:49:11 +02:00
|
|
|
match self.kind() {
|
2018-08-22 01:35:02 +01:00
|
|
|
ty::RawPtr(ref tm) => tm.visit_with(visitor),
|
2020-10-21 14:22:44 +02:00
|
|
|
ty::Array(typ, sz) => {
|
|
|
|
typ.visit_with(visitor)?;
|
|
|
|
sz.visit_with(visitor)
|
|
|
|
}
|
2018-08-22 01:35:02 +01:00
|
|
|
ty::Slice(typ) => typ.visit_with(visitor),
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::Adt(_, args) => args.visit_with(visitor),
|
2022-04-13 16:11:28 -07:00
|
|
|
ty::Dynamic(ref trait_ty, ref reg, _) => {
|
2020-10-21 14:22:44 +02:00
|
|
|
trait_ty.visit_with(visitor)?;
|
|
|
|
reg.visit_with(visitor)
|
2019-12-22 17:42:04 -05:00
|
|
|
}
|
2018-08-22 01:35:02 +01:00
|
|
|
ty::Tuple(ts) => ts.visit_with(visitor),
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::FnDef(_, args) => args.visit_with(visitor),
|
2018-08-22 01:35:02 +01:00
|
|
|
ty::FnPtr(ref f) => f.visit_with(visitor),
|
2020-10-21 14:22:44 +02:00
|
|
|
ty::Ref(r, ty, _) => {
|
|
|
|
r.visit_with(visitor)?;
|
|
|
|
ty.visit_with(visitor)
|
|
|
|
}
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::Generator(_did, ref args, _) => args.visit_with(visitor),
|
2018-08-22 01:35:02 +01:00
|
|
|
ty::GeneratorWitness(ref types) => types.visit_with(visitor),
|
2023-07-11 22:35:29 +01:00
|
|
|
ty::GeneratorWitnessMIR(_did, ref args) => args.visit_with(visitor),
|
|
|
|
ty::Closure(_did, ref args) => args.visit_with(visitor),
|
2022-11-27 17:52:17 +00:00
|
|
|
ty::Alias(_, ref data) => data.visit_with(visitor),
|
2018-10-22 20:37:56 +02:00
|
|
|
|
|
|
|
ty::Bool
|
|
|
|
| ty::Char
|
|
|
|
| ty::Str
|
|
|
|
| ty::Int(_)
|
|
|
|
| ty::Uint(_)
|
|
|
|
| ty::Float(_)
|
2020-05-05 23:02:09 -05:00
|
|
|
| ty::Error(_)
|
2018-10-22 20:37:56 +02:00
|
|
|
| ty::Infer(_)
|
|
|
|
| ty::Bound(..)
|
2018-11-02 18:48:24 +01:00
|
|
|
| ty::Placeholder(..)
|
2018-10-22 20:37:56 +02:00
|
|
|
| ty::Param(..)
|
|
|
|
| ty::Never
|
2023-01-17 23:17:13 -08:00
|
|
|
| ty::Foreign(..) => ControlFlow::Continue(()),
|
2015-11-18 09:38:57 +00:00
|
|
|
}
|
|
|
|
}
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for ty::Region<'tcx> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
folder.try_fold_region(self)
|
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2015-09-06 21:51:58 +03:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for ty::Region<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
visitor.visit_region(*self)
|
2015-09-06 21:51:58 +03:00
|
|
|
}
|
2016-01-06 02:01:28 +00:00
|
|
|
}
|
2015-11-18 09:38:57 +00:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for ty::Predicate<'tcx> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2021-12-01 00:55:57 +00:00
|
|
|
folder.try_fold_predicate(self)
|
2021-07-19 12:13:25 +02:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2021-07-19 12:13:25 +02:00
|
|
|
|
2023-06-16 06:27:41 +00:00
|
|
|
// FIXME(clause): This is wonky
|
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for ty::Clause<'tcx> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2023-06-19 20:48:46 +00:00
|
|
|
Ok(folder.try_fold_predicate(self.as_predicate())?.expect_clause())
|
2023-06-16 06:27:41 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for ty::Predicate<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
2020-06-10 09:30:39 +01:00
|
|
|
visitor.visit_predicate(*self)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-06-16 06:27:41 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for ty::Clause<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
|
|
|
visitor.visit_predicate(self.as_predicate())
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-11 09:13:27 +00:00
|
|
|
impl<'tcx> TypeSuperFoldable<TyCtxt<'tcx>> for ty::Predicate<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn try_super_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
2021-12-01 00:55:57 +00:00
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
let new = self.kind().try_fold_with(folder)?;
|
2023-02-11 09:18:12 +00:00
|
|
|
Ok(folder.interner().reuse_or_mk_predicate(self, new))
|
2017-05-23 04:19:47 -04:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2017-05-23 04:19:47 -04:00
|
|
|
|
2023-02-09 19:38:07 +00:00
|
|
|
impl<'tcx> TypeSuperVisitable<TyCtxt<'tcx>> for ty::Predicate<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn super_visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
self.kind().visit_with(visitor)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-06-19 20:46:46 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for &'tcx ty::List<ty::Clause<'tcx>> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
|
|
|
ty::util::fold_list(self, folder, |tcx, v| tcx.mk_clauses(v))
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for ty::Const<'tcx> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
folder.try_fold_const(self)
|
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for ty::Const<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
Folding revamp.
This commit makes type folding more like the way chalk does it.
Currently, `TypeFoldable` has `fold_with` and `super_fold_with` methods.
- `fold_with` is the standard entry point, and defaults to calling
`super_fold_with`.
- `super_fold_with` does the actual work of traversing a type.
- For a few types of interest (`Ty`, `Region`, etc.) `fold_with` instead
calls into a `TypeFolder`, which can then call back into
`super_fold_with`.
With the new approach, `TypeFoldable` has `fold_with` and
`TypeSuperFoldable` has `super_fold_with`.
- `fold_with` is still the standard entry point, *and* it does the
actual work of traversing a type, for all types except types of
interest.
- `super_fold_with` is only implemented for the types of interest.
Benefits of the new model.
- I find it easier to understand. The distinction between types of
interest and other types is clearer, and `super_fold_with` doesn't
exist for most types.
- With the current model is easy to get confused and implement a
`super_fold_with` method that should be left defaulted. (Some of the
precursor commits fixed such cases.)
- With the current model it's easy to call `super_fold_with` within
`TypeFolder` impls where `fold_with` should be called. The new
approach makes this mistake impossible, and this commit fixes a number
of such cases.
- It's potentially faster, because it avoids the `fold_with` ->
`super_fold_with` call in all cases except types of interest. A lot of
the time the compile would inline those away, but not necessarily
always.
2022-06-02 11:38:15 +10:00
|
|
|
visitor.visit_const(*self)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-11 09:13:27 +00:00
|
|
|
impl<'tcx> TypeSuperFoldable<TyCtxt<'tcx>> for ty::Const<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn try_super_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
2021-12-01 00:55:57 +00:00
|
|
|
self,
|
|
|
|
folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2022-02-02 14:24:45 +11:00
|
|
|
let ty = self.ty().try_fold_with(folder)?;
|
2023-07-04 15:41:45 +01:00
|
|
|
let kind = match self.kind() {
|
|
|
|
ConstKind::Param(p) => ConstKind::Param(p.try_fold_with(folder)?),
|
|
|
|
ConstKind::Infer(i) => ConstKind::Infer(i.try_fold_with(folder)?),
|
|
|
|
ConstKind::Bound(d, b) => {
|
|
|
|
ConstKind::Bound(d.try_fold_with(folder)?, b.try_fold_with(folder)?)
|
|
|
|
}
|
|
|
|
ConstKind::Placeholder(p) => ConstKind::Placeholder(p.try_fold_with(folder)?),
|
|
|
|
ConstKind::Unevaluated(uv) => ConstKind::Unevaluated(uv.try_fold_with(folder)?),
|
|
|
|
ConstKind::Value(v) => ConstKind::Value(v.try_fold_with(folder)?),
|
|
|
|
ConstKind::Error(e) => ConstKind::Error(e.try_fold_with(folder)?),
|
|
|
|
ConstKind::Expr(e) => ConstKind::Expr(e.try_fold_with(folder)?),
|
|
|
|
};
|
2022-06-10 11:18:06 +10:00
|
|
|
if ty != self.ty() || kind != self.kind() {
|
2023-07-04 14:26:19 +01:00
|
|
|
Ok(folder.interner().mk_ct_from_kind(kind, ty))
|
2020-05-31 17:16:44 +02:00
|
|
|
} else {
|
2021-05-19 13:34:54 +02:00
|
|
|
Ok(self)
|
2020-05-31 17:16:44 +02:00
|
|
|
}
|
2018-12-11 19:56:59 +01:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2018-12-11 19:56:59 +01:00
|
|
|
|
2023-02-09 19:38:07 +00:00
|
|
|
impl<'tcx> TypeSuperVisitable<TyCtxt<'tcx>> for ty::Const<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn super_visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
2022-02-02 14:24:45 +11:00
|
|
|
self.ty().visit_with(visitor)?;
|
2023-07-04 15:41:45 +01:00
|
|
|
match self.kind() {
|
|
|
|
ConstKind::Param(p) => p.visit_with(visitor),
|
|
|
|
ConstKind::Infer(i) => i.visit_with(visitor),
|
|
|
|
ConstKind::Bound(d, b) => {
|
|
|
|
d.visit_with(visitor)?;
|
|
|
|
b.visit_with(visitor)
|
|
|
|
}
|
|
|
|
ConstKind::Placeholder(p) => p.visit_with(visitor),
|
|
|
|
ConstKind::Unevaluated(uv) => uv.visit_with(visitor),
|
|
|
|
ConstKind::Value(v) => v.visit_with(visitor),
|
|
|
|
ConstKind::Error(e) => e.visit_with(visitor),
|
|
|
|
ConstKind::Expr(e) => e.visit_with(visitor),
|
|
|
|
}
|
2017-08-04 11:25:13 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeFoldable<TyCtxt<'tcx>> for InferConst<'tcx> {
|
|
|
|
fn try_fold_with<F: FallibleTypeFolder<TyCtxt<'tcx>>>(
|
|
|
|
self,
|
|
|
|
_folder: &mut F,
|
|
|
|
) -> Result<Self, F::Error> {
|
2021-05-19 13:34:54 +02:00
|
|
|
Ok(self)
|
2019-05-06 14:05:26 +01:00
|
|
|
}
|
2022-06-17 12:09:23 +01:00
|
|
|
}
|
2019-05-06 14:05:26 +01:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for InferConst<'tcx> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
_visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
2023-01-17 23:17:13 -08:00
|
|
|
ControlFlow::Continue(())
|
2019-05-06 14:05:26 +01:00
|
|
|
}
|
|
|
|
}
|
2022-01-12 23:29:10 +00:00
|
|
|
|
2023-02-09 19:38:07 +00:00
|
|
|
impl<'tcx> TypeSuperVisitable<TyCtxt<'tcx>> for ty::UnevaluatedConst<'tcx> {
|
2023-02-22 02:18:40 +00:00
|
|
|
fn super_visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(
|
|
|
|
&self,
|
|
|
|
visitor: &mut V,
|
|
|
|
) -> ControlFlow<V::BreakTy> {
|
2023-07-11 22:35:29 +01:00
|
|
|
self.args.visit_with(visitor)
|
2022-01-12 23:29:10 +00:00
|
|
|
}
|
|
|
|
}
|
2023-01-22 17:06:28 -05:00
|
|
|
|
2023-02-22 02:18:40 +00:00
|
|
|
impl<'tcx> TypeVisitable<TyCtxt<'tcx>> for TyAndLayout<'tcx, Ty<'tcx>> {
|
|
|
|
fn visit_with<V: TypeVisitor<TyCtxt<'tcx>>>(&self, visitor: &mut V) -> ControlFlow<V::BreakTy> {
|
2023-01-22 17:06:28 -05:00
|
|
|
visitor.visit_ty(self.ty)
|
|
|
|
}
|
|
|
|
}
|