You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I noticed the following behaviour: if I insert a line break into my const definition, the highlighting and "underlining" behaviour of the "unused" warning changes. It confused me for the first moment, since I thought I spelled const wrong.
warning: constant item is never used: `IND_TOP_RIGHT`, #[warn(dead_code)] on by default
--> src/lib.rs:191:1
|
191 | const IND_TOP_RIGHT: usize =
| ^
vs.
warning: constant item is never used: `IND_TOP_RIGHT`, #[warn(dead_code)] on by default
--> src/lib.rs:191:1
|
191 | const IND_TOP_RIGHT: usize = 5;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Wouldn't it be better if only the constants name was highlighted anyway?
The text was updated successfully, but these errors were encountered:
fabric-and-ink
changed the title
Warning message formatting: unused const var
Warning message formatting: unused const
Oct 22, 2016
Hello!
I noticed the following behaviour: if I insert a line break into my
const
definition, the highlighting and "underlining" behaviour of the "unused" warning changes. It confused me for the first moment, since I thought I spelledconst
wrong.vs.
Wouldn't it be better if only the constants name was highlighted anyway?
The text was updated successfully, but these errors were encountered: