rust/tests/ui/macros/macro-with-attrs2.rs

//@ run-pass

#[cfg(FALSE)]
macro_rules! foo { () => (1) }

#[cfg(not(FALSE))]
macro_rules! foo { () => (2) }

pub fn main() {
    assert_eq!(foo!(), 2);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00
Unify all the always-false cfgs under the `FALSE` cfg 2024-04-07 00:43:00 +02:00			`#[cfg(FALSE)]`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`macro_rules! foo { () => (1) }`
Allow attributes on macros It's unclear to me why these currently aren't allowed, and my best guess is that a long time ago we didn't strip the ast of cfg nodes before syntax expansion. Now that this is done, I'm not certain that we should continue to prohibit this functionality. This is a step in the right direction towards #5605, because now we can add an empty `std::macros` module to the documentation with a bunch of empty macros explaining how they're supposed to be used. 2013-10-07 15:40:46 -07:00
Unify all the always-false cfgs under the `FALSE` cfg 2024-04-07 00:43:00 +02:00			`#[cfg(not(FALSE))]`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`macro_rules! foo { () => (2) }`
Allow attributes on macros It's unclear to me why these currently aren't allowed, and my best guess is that a long time ago we didn't strip the ast of cfg nodes before syntax expansion. Now that this is done, I'm not certain that we should continue to prohibit this functionality. This is a step in the right direction towards #5605, because now we can add an empty `std::macros` module to the documentation with a bunch of empty macros explaining how they're supposed to be used. 2013-10-07 15:40:46 -07:00
			`pub fn main() {`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`assert_eq!(foo!(), 2);`
Allow attributes on macros It's unclear to me why these currently aren't allowed, and my best guess is that a long time ago we didn't strip the ast of cfg nodes before syntax expansion. Now that this is done, I'm not certain that we should continue to prohibit this functionality. This is a step in the right direction towards #5605, because now we can add an empty `std::macros` module to the documentation with a bunch of empty macros explaining how they're supposed to be used. 2013-10-07 15:40:46 -07:00			`}`