mirror of
https://github.com/rust-lang/rust.git
synced 2025-10-31 21:16:44 +00:00
114 lines
3.7 KiB
Rust
114 lines
3.7 KiB
Rust
/// A macro for triggering an ICE.
|
|
/// Calling `bug` instead of panicking will result in a nicer error message and should
|
|
/// therefore be preferred 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, [`DiagCtxtHandle::span_delayed_bug`]
|
|
/// may be useful.
|
|
///
|
|
/// [`DiagCtxtHandle::span_delayed_bug`]: rustc_errors::DiagCtxtHandle::span_delayed_bug
|
|
/// [`span_bug`]: crate::span_bug
|
|
#[macro_export]
|
|
macro_rules! bug {
|
|
() => (
|
|
$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)+))
|
|
);
|
|
}
|
|
|
|
/// 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, [`DiagCtxtHandle::span_delayed_bug`]
|
|
/// may be useful.
|
|
///
|
|
/// [`DiagCtxtHandle::span_delayed_bug`]: rustc_errors::DiagCtxtHandle::span_delayed_bug
|
|
#[macro_export]
|
|
macro_rules! span_bug {
|
|
($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)+))
|
|
);
|
|
}
|
|
|
|
///////////////////////////////////////////////////////////////////////////
|
|
// Lift and TypeFoldable/TypeVisitable macros
|
|
//
|
|
// When possible, use one of these (relatively) convenient macros to write
|
|
// the impls for you.
|
|
|
|
#[macro_export]
|
|
macro_rules! TrivialLiftImpls {
|
|
($($ty:ty),+ $(,)?) => {
|
|
$(
|
|
impl<'tcx> $crate::ty::Lift<$crate::ty::TyCtxt<'tcx>> for $ty {
|
|
type Lifted = Self;
|
|
fn lift_to_interner(self, _: $crate::ty::TyCtxt<'tcx>) -> Option<Self> {
|
|
Some(self)
|
|
}
|
|
}
|
|
)+
|
|
};
|
|
}
|
|
|
|
/// Used for types that are `Copy` and which **do not care arena
|
|
/// allocated data** (i.e., don't need to be folded).
|
|
#[macro_export]
|
|
macro_rules! TrivialTypeTraversalImpls {
|
|
($($ty:ty),+ $(,)?) => {
|
|
$(
|
|
impl<'tcx> $crate::ty::fold::TypeFoldable<$crate::ty::TyCtxt<'tcx>> for $ty {
|
|
fn try_fold_with<F: $crate::ty::fold::FallibleTypeFolder<$crate::ty::TyCtxt<'tcx>>>(
|
|
self,
|
|
_: &mut F,
|
|
) -> ::std::result::Result<Self, F::Error> {
|
|
Ok(self)
|
|
}
|
|
|
|
#[inline]
|
|
fn fold_with<F: $crate::ty::fold::TypeFolder<$crate::ty::TyCtxt<'tcx>>>(
|
|
self,
|
|
_: &mut F,
|
|
) -> Self {
|
|
self
|
|
}
|
|
}
|
|
|
|
impl<'tcx> $crate::ty::visit::TypeVisitable<$crate::ty::TyCtxt<'tcx>> for $ty {
|
|
#[inline]
|
|
fn visit_with<F: $crate::ty::visit::TypeVisitor<$crate::ty::TyCtxt<'tcx>>>(
|
|
&self,
|
|
_: &mut F)
|
|
-> F::Result
|
|
{
|
|
<F::Result as ::rustc_ast_ir::visit::VisitorResult>::output()
|
|
}
|
|
}
|
|
)+
|
|
};
|
|
}
|
|
|
|
#[macro_export]
|
|
macro_rules! TrivialTypeTraversalAndLiftImpls {
|
|
($($t:tt)*) => {
|
|
TrivialTypeTraversalImpls! { $($t)* }
|
|
TrivialLiftImpls! { $($t)* }
|
|
}
|
|
}
|