rust/tests/ui/macros/cfg.rs

fn main() {
    cfg!(); //~ ERROR macro requires a cfg-pattern
    cfg!(123); //~ ERROR literal in `cfg` predicate value must be a boolean
    cfg!(foo = 123); //~ ERROR literal in `cfg` predicate value must be a string
    cfg!(foo, bar); //~ ERROR expected 1 cfg-pattern
}
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			`fn main() {`
			`cfg!(); //~ ERROR macro requires a cfg-pattern`
Improve non-boolean literal error in cfg predicate 2024-10-01 08:25:18 +00:00			cfg!(123); //~ ERROR literal in `cfg` predicate value must be a boolean
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			cfg!(foo = 123); //~ ERROR literal in `cfg` predicate value must be a string
Add UI test for `cfg!(foo, bar)` 2022-06-21 18:28:22 +00:00			`cfg!(foo, bar); //~ ERROR expected 1 cfg-pattern`
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			`}`