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

// run-pass
// compile-flags: --cfg foo


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

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

pub fn main() {
    assert_eq!(foo!(), 1);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 12:18:55 +00:00			`// run-pass`
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 22:40:46 +00:00			`// compile-flags: --cfg foo`
Fix damage done by the pretty-printer 2011-07-27 12:48:34 +00:00
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 20:13:15 +00:00
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 22:40:46 +00:00			`#[cfg(foo)]`
Remove all `i` suffixes 2015-01-25 21:05:03 +00: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 22:40:46 +00:00
			`#[cfg(not(foo))]`
Remove all `i` suffixes 2015-01-25 21:05:03 +00: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 22:40:46 +00:00
test: Make all the run-pass tests use `pub fn main` 2014-01-03 23:30:54 +00:00			`pub fn main() {`
Remove all `i` suffixes 2015-01-25 21:05:03 +00:00			`assert_eq!(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 22:40:46 +00:00			`}`