rust/tests/ui/macros/issue-78333.rs

//@ build-pass

#![no_implicit_prelude]

fn main() {
    ::std::panic!();
    ::std::todo!();
    ::std::unimplemented!();
    ::std::assert_eq!(0, 0);
    ::std::assert_ne!(0, 1);
    ::std::dbg!(123);
    ::std::unreachable!();
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ build-pass`
Qualify `panic!` as `core::panic!` in non-built-in `core` macros Otherwise code like this #![no_implicit_prelude] fn main() { ::std::todo!(); ::std::unimplemented!(); } will fail to compile, which is unfortunate and presumably unintended. This changes many invocations of `panic!` in a `macro_rules!` definition to invocations of `$crate::panic!`, which makes the invocations hygienic. Note that this does not make the built-in macro `assert!` hygienic. 2020-10-24 18:35:46 -07:00
			`#![no_implicit_prelude]`

			`fn main() {`
			`::std::panic!();`
			`::std::todo!();`
			`::std::unimplemented!();`
			`::std::assert_eq!(0, 0);`
			`::std::assert_ne!(0, 1);`
			`::std::dbg!(123);`
			`::std::unreachable!();`
			`}`