rust/src/test/ui/lint/dead-code/empty-unused-enum.stderr

error: enum is never used: `E`
  --> $DIR/empty-unused-enum.rs:3:6
   |
LL | enum E {}
   |      ^
   |
note: the lint level is defined here
  --> $DIR/empty-unused-enum.rs:1:9
   |
LL | #![deny(unused)]
   |         ^^^^^^
   = note: `#[deny(dead_code)]` implied by `#[deny(unused)]`

error: aborting due to previous error
Add more tests covering more cases 2019-08-21 18:30:11 -05:00			error: enum is never used: `E`
Use ident instead of def_span in dead-code pass According to @estebank, def_span scans forward on the line until it finds a {, and if it can't find one, fallse back to the span for the whole item. This was apparently written before the identifier span was explicitly tracked on each node. This means that if an unused function signature spans multiple lines, the entire function (potentially hundreds of lines) gets flagged as dead code. This could, for example, cause IDEs to add error squiggly's to the whole function. By using the span from the ident instead, we narrow the scope of this in most cases. In a wider sense, it's probably safe to use ident.span instead of def_span in most locations throughout the whole code base, but since this is my first contribution, I kept it small. Some interesting points that came up while I was working on this: - I reorganized the tests a bit to bring some of the dead code ones all into the same location - A few tests were for things unrelated to dead code (like the path-lookahead for parens), so I added #![allow(dead_code)] and cleaned up the stderr file to reduce noise in the future - The same fix doesn't apply to const and static declarations. I tried adding these cases to the match expression, but that created a much wider change to tests and error messages, so I left it off until I could get some code review to validate the approach. 2019-10-25 13:46:07 -05:00			`--> $DIR/empty-unused-enum.rs:3:6`
Add more tests covering more cases 2019-08-21 18:30:11 -05:00			`\|`
			`LL \| enum E {}`
Use ident instead of def_span in dead-code pass According to @estebank, def_span scans forward on the line until it finds a {, and if it can't find one, fallse back to the span for the whole item. This was apparently written before the identifier span was explicitly tracked on each node. This means that if an unused function signature spans multiple lines, the entire function (potentially hundreds of lines) gets flagged as dead code. This could, for example, cause IDEs to add error squiggly's to the whole function. By using the span from the ident instead, we narrow the scope of this in most cases. In a wider sense, it's probably safe to use ident.span instead of def_span in most locations throughout the whole code base, but since this is my first contribution, I kept it small. Some interesting points that came up while I was working on this: - I reorganized the tests a bit to bring some of the dead code ones all into the same location - A few tests were for things unrelated to dead code (like the path-lookahead for parens), so I added #![allow(dead_code)] and cleaned up the stderr file to reduce noise in the future - The same fix doesn't apply to const and static declarations. I tried adding these cases to the match expression, but that created a much wider change to tests and error messages, so I left it off until I could get some code review to validate the approach. 2019-10-25 13:46:07 -05:00			`\| ^`
Add more tests covering more cases 2019-08-21 18:30:11 -05:00			`\|`
Normalise notes with the/is 2020-01-22 17:57:38 -06:00			`note: the lint level is defined here`
Move dead_code related tests to test/ui/dead-code This helps organize the tests better. I also renamed several of the tests to remove redundant dead-code in the path, and better match what they're testing 2019-10-24 23:42:05 -05:00			`--> $DIR/empty-unused-enum.rs:1:9`
Add more tests covering more cases 2019-08-21 18:30:11 -05:00			`\|`
			`LL \| #![deny(unused)]`
			`\| ^^^^^^`
			= note: `#[deny(dead_code)]` implied by `#[deny(unused)]`

			`error: aborting due to previous error`