2022-12-30 06:38:34 -06:00
|
|
|
/// A macro for triggering an ICE.
|
|
|
|
/// Calling `bug` instead of panicking will result in a nicer error message and should
|
|
|
|
/// therefore be prefered over `panic`/`unreachable` or others.
|
|
|
|
///
|
|
|
|
/// If you have a span available, you should use [`span_bug`] instead.
|
|
|
|
///
|
|
|
|
/// If the bug should only be emitted when compilation didn't fail, [`Session::delay_span_bug`] may be useful.
|
|
|
|
///
|
|
|
|
/// [`Session::delay_span_bug`]: rustc_session::Session::delay_span_bug
|
|
|
|
/// [`span_bug`]: crate::span_bug
|
2016-03-23 18:35:26 -05:00
|
|
|
#[macro_export]
|
|
|
|
macro_rules! bug {
|
2020-06-15 09:17:58 -05:00
|
|
|
() => ( $crate::bug!("impossible case reached") );
|
|
|
|
($msg:expr) => ({ $crate::util::bug::bug_fmt(::std::format_args!($msg)) });
|
|
|
|
($msg:expr,) => ({ $crate::bug!($msg) });
|
|
|
|
($fmt:expr, $($arg:tt)+) => ({
|
|
|
|
$crate::util::bug::bug_fmt(::std::format_args!($fmt, $($arg)+))
|
|
|
|
});
|
2016-03-23 18:35:26 -05:00
|
|
|
}
|
|
|
|
|
2022-12-30 06:38:34 -06:00
|
|
|
/// A macro for triggering an ICE with a span.
|
|
|
|
/// Calling `span_bug!` instead of panicking will result in a nicer error message and point
|
|
|
|
/// at the code the compiler was compiling when it ICEd. This is the preferred way to trigger
|
|
|
|
/// ICEs.
|
|
|
|
///
|
|
|
|
/// If the bug should only be emitted when compilation didn't fail, [`Session::delay_span_bug`] may be useful.
|
|
|
|
///
|
|
|
|
/// [`Session::delay_span_bug`]: rustc_session::Session::delay_span_bug
|
2016-03-23 18:35:26 -05:00
|
|
|
#[macro_export]
|
|
|
|
macro_rules! span_bug {
|
2020-06-15 09:17:58 -05:00
|
|
|
($span:expr, $msg:expr) => ({ $crate::util::bug::span_bug_fmt($span, ::std::format_args!($msg)) });
|
|
|
|
($span:expr, $msg:expr,) => ({ $crate::span_bug!($span, $msg) });
|
|
|
|
($span:expr, $fmt:expr, $($arg:tt)+) => ({
|
|
|
|
$crate::util::bug::span_bug_fmt($span, ::std::format_args!($fmt, $($arg)+))
|
|
|
|
});
|
2016-03-23 18:35:26 -05:00
|
|
|
}
|
2017-03-30 08:27:27 -05:00
|
|
|
|
2018-02-09 09:34:23 -06:00
|
|
|
///////////////////////////////////////////////////////////////////////////
|
2022-06-17 05:05:17 -05:00
|
|
|
// Lift and TypeFoldable/TypeVisitable macros
|
2018-02-09 09:34:23 -06:00
|
|
|
//
|
|
|
|
// When possible, use one of these (relatively) convenient macros to write
|
|
|
|
// the impls for you.
|
|
|
|
|
|
|
|
#[macro_export]
|
|
|
|
macro_rules! CloneLiftImpls {
|
|
|
|
(for <$tcx:lifetime> { $($ty:ty,)+ }) => {
|
|
|
|
$(
|
|
|
|
impl<$tcx> $crate::ty::Lift<$tcx> for $ty {
|
|
|
|
type Lifted = Self;
|
2020-10-16 14:59:49 -05:00
|
|
|
fn lift_to_tcx(self, _: $crate::ty::TyCtxt<$tcx>) -> Option<Self> {
|
|
|
|
Some(self)
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
|
|
|
}
|
|
|
|
)+
|
|
|
|
};
|
|
|
|
|
|
|
|
($($ty:ty,)+) => {
|
|
|
|
CloneLiftImpls! {
|
|
|
|
for <'tcx> {
|
|
|
|
$($ty,)+
|
|
|
|
}
|
|
|
|
}
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Used for types that are `Copy` and which **do not care arena
|
|
|
|
/// allocated data** (i.e., don't need to be folded).
|
|
|
|
#[macro_export]
|
2022-06-17 05:05:17 -05:00
|
|
|
macro_rules! TrivialTypeTraversalImpls {
|
2018-02-09 09:34:23 -06:00
|
|
|
(for <$tcx:lifetime> { $($ty:ty,)+ }) => {
|
|
|
|
$(
|
|
|
|
impl<$tcx> $crate::ty::fold::TypeFoldable<$tcx> for $ty {
|
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-01 20:38:15 -05:00
|
|
|
fn try_fold_with<F: $crate::ty::fold::FallibleTypeFolder<$tcx>>(
|
2020-10-23 19:21:18 -05:00
|
|
|
self,
|
2022-10-05 11:26:48 -05:00
|
|
|
_: &mut F,
|
|
|
|
) -> ::std::result::Result<Self, F::Error> {
|
2021-05-19 06:34:54 -05:00
|
|
|
Ok(self)
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
2022-10-05 11:26:48 -05:00
|
|
|
|
|
|
|
#[inline]
|
|
|
|
fn fold_with<F: $crate::ty::fold::TypeFolder<$tcx>>(
|
|
|
|
self,
|
|
|
|
_: &mut F,
|
|
|
|
) -> Self {
|
|
|
|
self
|
|
|
|
}
|
2022-06-17 05:05:17 -05:00
|
|
|
}
|
2018-02-09 09:34:23 -06:00
|
|
|
|
2022-06-17 05:05:17 -05:00
|
|
|
impl<$tcx> $crate::ty::visit::TypeVisitable<$tcx> for $ty {
|
2022-10-05 11:26:48 -05:00
|
|
|
#[inline]
|
2022-06-17 05:05:17 -05:00
|
|
|
fn visit_with<F: $crate::ty::visit::TypeVisitor<$tcx>>(
|
2018-02-09 09:34:23 -06:00
|
|
|
&self,
|
|
|
|
_: &mut F)
|
2020-11-05 10:30:39 -06:00
|
|
|
-> ::std::ops::ControlFlow<F::BreakTy>
|
2018-02-09 09:34:23 -06:00
|
|
|
{
|
2023-01-18 01:17:13 -06:00
|
|
|
::std::ops::ControlFlow::Continue(())
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
|
|
|
}
|
|
|
|
)+
|
|
|
|
};
|
|
|
|
|
|
|
|
($($ty:ty,)+) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
TrivialTypeTraversalImpls! {
|
2018-02-09 09:34:23 -06:00
|
|
|
for <'tcx> {
|
|
|
|
$($ty,)+
|
|
|
|
}
|
|
|
|
}
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
#[macro_export]
|
2022-06-17 05:05:17 -05:00
|
|
|
macro_rules! TrivialTypeTraversalAndLiftImpls {
|
2018-02-09 09:34:23 -06:00
|
|
|
($($t:tt)*) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
TrivialTypeTraversalImpls! { $($t)* }
|
2018-02-09 09:34:23 -06:00
|
|
|
CloneLiftImpls! { $($t)* }
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
#[macro_export]
|
2022-06-17 05:05:17 -05:00
|
|
|
macro_rules! EnumTypeTraversalImpl {
|
2018-02-09 09:34:23 -06:00
|
|
|
(impl<$($p:tt),*> TypeFoldable<$tcx:tt> for $s:path {
|
|
|
|
$($variants:tt)*
|
|
|
|
} $(where $($wc:tt)*)*) => {
|
|
|
|
impl<$($p),*> $crate::ty::fold::TypeFoldable<$tcx> for $s
|
|
|
|
$(where $($wc)*)*
|
|
|
|
{
|
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-01 20:38:15 -05:00
|
|
|
fn try_fold_with<V: $crate::ty::fold::FallibleTypeFolder<$tcx>>(
|
2020-10-23 19:21:18 -05:00
|
|
|
self,
|
2018-02-09 09:34:23 -06:00
|
|
|
folder: &mut V,
|
2021-05-19 06:34:54 -05:00
|
|
|
) -> ::std::result::Result<Self, V::Error> {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(@FoldVariants(self, folder) input($($variants)*) output())
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
2022-06-17 05:05:17 -05:00
|
|
|
}
|
|
|
|
};
|
2018-02-09 09:34:23 -06:00
|
|
|
|
2022-06-17 05:05:17 -05:00
|
|
|
(impl<$($p:tt),*> TypeVisitable<$tcx:tt> for $s:path {
|
|
|
|
$($variants:tt)*
|
|
|
|
} $(where $($wc:tt)*)*) => {
|
|
|
|
impl<$($p),*> $crate::ty::visit::TypeVisitable<$tcx> for $s
|
|
|
|
$(where $($wc)*)*
|
|
|
|
{
|
|
|
|
fn visit_with<V: $crate::ty::visit::TypeVisitor<$tcx>>(
|
2018-02-09 09:34:23 -06:00
|
|
|
&self,
|
|
|
|
visitor: &mut V,
|
2020-11-05 10:30:39 -06:00
|
|
|
) -> ::std::ops::ControlFlow<V::BreakTy> {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(@VisitVariants(self, visitor) input($($variants)*) output())
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
(@FoldVariants($this:expr, $folder:expr) input() output($($output:tt)*)) => {
|
2021-05-19 06:34:54 -05:00
|
|
|
Ok(match $this {
|
2018-02-09 09:34:23 -06:00
|
|
|
$($output)*
|
2021-05-19 06:34:54 -05:00
|
|
|
})
|
2018-02-09 09:34:23 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
(@FoldVariants($this:expr, $folder:expr)
|
|
|
|
input( ($variant:path) ( $($variant_arg:ident),* ) , $($input:tt)*)
|
|
|
|
output( $($output:tt)*) ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(
|
2018-02-09 09:34:23 -06:00
|
|
|
@FoldVariants($this, $folder)
|
|
|
|
input($($input)*)
|
|
|
|
output(
|
|
|
|
$variant ( $($variant_arg),* ) => {
|
|
|
|
$variant (
|
2021-11-30 18:55:57 -06:00
|
|
|
$($crate::ty::fold::TypeFoldable::try_fold_with($variant_arg, $folder)?),*
|
2018-02-09 09:34:23 -06:00
|
|
|
)
|
|
|
|
}
|
|
|
|
$($output)*
|
|
|
|
)
|
|
|
|
)
|
|
|
|
};
|
|
|
|
|
|
|
|
(@FoldVariants($this:expr, $folder:expr)
|
2019-02-24 06:59:44 -06:00
|
|
|
input( ($variant:path) { $($variant_arg:ident),* $(,)? } , $($input:tt)*)
|
2018-02-09 09:34:23 -06:00
|
|
|
output( $($output:tt)*) ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(
|
2018-02-09 09:34:23 -06:00
|
|
|
@FoldVariants($this, $folder)
|
|
|
|
input($($input)*)
|
|
|
|
output(
|
|
|
|
$variant { $($variant_arg),* } => {
|
|
|
|
$variant {
|
|
|
|
$($variant_arg: $crate::ty::fold::TypeFoldable::fold_with(
|
|
|
|
$variant_arg, $folder
|
2021-05-19 06:34:54 -05:00
|
|
|
)?),* }
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
|
|
|
$($output)*
|
|
|
|
)
|
|
|
|
)
|
|
|
|
};
|
|
|
|
|
|
|
|
(@FoldVariants($this:expr, $folder:expr)
|
|
|
|
input( ($variant:path), $($input:tt)*)
|
|
|
|
output( $($output:tt)*) ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(
|
2018-02-09 09:34:23 -06:00
|
|
|
@FoldVariants($this, $folder)
|
|
|
|
input($($input)*)
|
|
|
|
output(
|
|
|
|
$variant => { $variant }
|
|
|
|
$($output)*
|
|
|
|
)
|
|
|
|
)
|
|
|
|
};
|
|
|
|
|
|
|
|
(@VisitVariants($this:expr, $visitor:expr) input() output($($output:tt)*)) => {
|
|
|
|
match $this {
|
|
|
|
$($output)*
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
(@VisitVariants($this:expr, $visitor:expr)
|
|
|
|
input( ($variant:path) ( $($variant_arg:ident),* ) , $($input:tt)*)
|
|
|
|
output( $($output:tt)*) ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(
|
2018-02-09 09:34:23 -06:00
|
|
|
@VisitVariants($this, $visitor)
|
|
|
|
input($($input)*)
|
|
|
|
output(
|
|
|
|
$variant ( $($variant_arg),* ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
$($crate::ty::visit::TypeVisitable::visit_with(
|
2018-02-09 09:34:23 -06:00
|
|
|
$variant_arg, $visitor
|
2020-10-21 07:22:44 -05:00
|
|
|
)?;)*
|
2023-01-18 01:17:13 -06:00
|
|
|
::std::ops::ControlFlow::Continue(())
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
|
|
|
$($output)*
|
|
|
|
)
|
|
|
|
)
|
|
|
|
};
|
|
|
|
|
|
|
|
(@VisitVariants($this:expr, $visitor:expr)
|
2019-02-24 06:59:44 -06:00
|
|
|
input( ($variant:path) { $($variant_arg:ident),* $(,)? } , $($input:tt)*)
|
2018-02-09 09:34:23 -06:00
|
|
|
output( $($output:tt)*) ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(
|
2018-02-09 09:34:23 -06:00
|
|
|
@VisitVariants($this, $visitor)
|
|
|
|
input($($input)*)
|
|
|
|
output(
|
|
|
|
$variant { $($variant_arg),* } => {
|
2022-06-17 05:05:17 -05:00
|
|
|
$($crate::ty::visit::TypeVisitable::visit_with(
|
2018-02-09 09:34:23 -06:00
|
|
|
$variant_arg, $visitor
|
2020-10-21 07:22:44 -05:00
|
|
|
)?;)*
|
2023-01-18 01:17:13 -06:00
|
|
|
::std::ops::ControlFlow::Continue(())
|
2018-02-09 09:34:23 -06:00
|
|
|
}
|
|
|
|
$($output)*
|
|
|
|
)
|
|
|
|
)
|
|
|
|
};
|
|
|
|
|
|
|
|
(@VisitVariants($this:expr, $visitor:expr)
|
|
|
|
input( ($variant:path), $($input:tt)*)
|
|
|
|
output( $($output:tt)*) ) => {
|
2022-06-17 05:05:17 -05:00
|
|
|
EnumTypeTraversalImpl!(
|
2018-02-09 09:34:23 -06:00
|
|
|
@VisitVariants($this, $visitor)
|
|
|
|
input($($input)*)
|
|
|
|
output(
|
2023-01-18 01:17:13 -06:00
|
|
|
$variant => { ::std::ops::ControlFlow::Continue(()) }
|
2018-02-09 09:34:23 -06:00
|
|
|
$($output)*
|
|
|
|
)
|
|
|
|
)
|
|
|
|
};
|
|
|
|
}
|