allman style brace formatting triggers suspicious_else_formatting #3864

Activity

1. flip1995 commented on Mar 10, 2019

   

   flip1995

   on Mar 10, 2019

   Member

   More actions

   Example:

   fn main() {
       if true 
       {
           println!("Hi");
       }
       else 
       {
           println!("Bye");
       }
   }

   Playground

   👍React with 👍2Reacted by misos1 and sdegutis
2. flip1995

   added

   C-bugCategory: Clippy is not doing the correct thingCategory: Clippy is not doing the correct thing

   on Mar 10, 2019
3. sdegutis commented on Jan 14, 2020

   

   sdegutis

   on Jan 14, 2020

   More actions

   I just switched to this style and now all my else-statements are being triggered. Is there at least a way to tell clippy to silence this warning for the whole project? I can't find what to put inside .clippy.toml to silence this, if any such thing exists.
4. flip1995 commented on Jan 16, 2020

   

   flip1995

   on Jan 16, 2020

   Member

   More actions

   clippy.toml doesn't and won't support allowing/denying lints. You can do this in the main.rs/lib.rs file with #![allow(clippy::suspicious_else_formatting)] at the top of the file.
5. phansch

   added

   I-false-positiveIssue: The lint was triggered on code it shouldn't haveIssue: The lint was triggered on code it shouldn't have

   on Dec 18, 2020
6. bors

   added a commit that references this issue on Dec 19, 2020

   Auto merge of #6473 - phansch:split-up-ui-test, r=flip1995

   ...

   0904f54
7. bors

   added a commit that references this issue on Apr 16, 2021

   Auto merge of #7087 - Jarcho:allman_style_else, r=camsteffen

   ...

   This issue will close once commit 831c157 is merged into the 'main' branch.

   831c157
8. bors

   closed this as completedin 831c157on Apr 16, 2021
9. chilabot commented on Dec 4, 2024

   

   chilabot

   on Dec 4, 2024

   More actions

   I prefer to put linting in the Cargo.toml file, in the lints.clippy section. More accessible and visually better.