rust/src/test/ui/span/macro-span-replacement.stderr

warning: struct is never constructed: `S`
  --> $DIR/macro-span-replacement.rs:7:14
   |
LL |         $b $a;
   |              ^
...
LL |     m!(S struct);
   |     ------------- in this macro invocation
   |
note: the lint level is defined here
  --> $DIR/macro-span-replacement.rs:3:9
   |
LL | #![warn(unused)]
   |         ^^^^^^
   = note: `#[warn(dead_code)]` implied by `#[warn(unused)]`
   = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
dead-code lint: say "constructed" for structs This is a sequel to November 2017's #46103 / 1a9dc2e9. It had been reported (more than once—at least #19140, #44083, and #44565) that the "never used" language was confusing for enum variants that were "used" as match patterns, so the wording was changed to say never "constructed" specifically for enum variants. More recently, the same issue was raised for structs (#52325). It seems consistent to say "constructed" here, too, for the same reasons. We considered using more specific word "called" for unused functions and methods (while we declined to do this in #46103, the rationale given in the commit message doesn't actually make sense), but it turns out that Cargo's test suite expects the "never used" message, and maybe we don't care enough even to make a Cargo PR over such a petty and subjective wording change. This resolves #52325. 2018-07-21 19:55:34 -05:00			warning: struct is never constructed: `S`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/macro-span-replacement.rs:7:14`
Use the macro structure spans instead of the invocation 2017-07-19 23:54:01 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| $b $a;`
Minimize weird spans involving macro context Sometimes the parser attempts to synthesize spans from within a macro context with the span for the captured argument, leading to non-sensical spans with very bad output. Given that an incorrect span is worse than a partially incomplete span, when detecting this situation return only one of the spans without mergin them. 2018-02-01 13:51:49 -06:00			`\| ^`
Use the macro structure spans instead of the invocation 2017-07-19 23:54:01 -05:00			`...`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| m!(S struct);`
Use the macro structure spans instead of the invocation 2017-07-19 23:54:01 -05:00			`\| ------------- in this macro invocation`
			`\|`
Normalise notes with the/is 2020-01-22 17:57:38 -06:00			`note: the lint level is defined here`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/macro-span-replacement.rs:3:9`
rustc: Rearchitect lints to be emitted more eagerly In preparation for incremental compilation this commit refactors the lint handling infrastructure in the compiler to be more "eager" and overall more incremental-friendly. Many passes of the compiler can emit lints at various points but before this commit all lints were buffered in a table to be emitted at the very end of compilation. This commit changes these lints to be emitted immediately during compilation using pre-calculated lint level-related data structures. Linting today is split into two phases, one set of "early" lints run on the `syntax::ast` and a "late" set of lints run on the HIR. This commit moves the "early" lints to running as late as possible in compilation, just before HIR lowering. This notably means that we're catching resolve-related lints just before HIR lowering. The early linting remains a pass very similar to how it was before, maintaining context of the current lint level as it walks the tree. Post-HIR, however, linting is structured as a method on the `TyCtxt` which transitively executes a query to calculate lint levels. Each request to lint on a `TyCtxt` will query the entire crate's 'lint level data structure' and then go from there about whether the lint should be emitted or not. The query depends on the entire HIR crate but should be very quick to calculate (just a quick walk of the HIR) and the red-green system should notice that the lint level data structure rarely changes, and should hopefully preserve incrementality. Overall this resulted in a pretty big change to the test suite now that lints are emitted much earlier in compilation (on-demand vs only at the end). This in turn necessitated the addition of many `#![allow(warnings)]` directives throughout the compile-fail test suite and a number of updates to the UI test suite. 2017-07-26 23:51:09 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| #![warn(unused)]`
rustc: Rearchitect lints to be emitted more eagerly In preparation for incremental compilation this commit refactors the lint handling infrastructure in the compiler to be more "eager" and overall more incremental-friendly. Many passes of the compiler can emit lints at various points but before this commit all lints were buffered in a table to be emitted at the very end of compilation. This commit changes these lints to be emitted immediately during compilation using pre-calculated lint level-related data structures. Linting today is split into two phases, one set of "early" lints run on the `syntax::ast` and a "late" set of lints run on the HIR. This commit moves the "early" lints to running as late as possible in compilation, just before HIR lowering. This notably means that we're catching resolve-related lints just before HIR lowering. The early linting remains a pass very similar to how it was before, maintaining context of the current lint level as it walks the tree. Post-HIR, however, linting is structured as a method on the `TyCtxt` which transitively executes a query to calculate lint levels. Each request to lint on a `TyCtxt` will query the entire crate's 'lint level data structure' and then go from there about whether the lint should be emitted or not. The query depends on the entire HIR crate but should be very quick to calculate (just a quick walk of the HIR) and the red-green system should notice that the lint level data structure rarely changes, and should hopefully preserve incrementality. Overall this resulted in a pretty big change to the test suite now that lints are emitted much earlier in compilation (on-demand vs only at the end). This in turn necessitated the addition of many `#![allow(warnings)]` directives throughout the compile-fail test suite and a number of updates to the UI test suite. 2017-07-26 23:51:09 -05:00			`\| ^^^^^^`
normalize use of backticks in compiler messages for librustc/lint https://github.com/rust-lang/rust/issues/60532 2019-07-16 15:17:38 -05:00			= note: `#[warn(dead_code)]` implied by `#[warn(unused)]`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06:00			`= note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)`
Use the macro structure spans instead of the invocation 2017-07-19 23:54:01 -05:00