@isrnick
There's also the 2 liner:
if (condition)
dosomething();
@bapoTV
Allman is really good for me to read correctly, it makes the code breathe and have some space with a clear indentation mark
@P0isonw0lf
Single lines for exclusions at the top of a function looks so much clearer, I need to start writing some :o
@soda24612
1. if statement 2. while loop that runs 1 time 3. for loop that runs one time 4. ternary operator 5. macros 6.if statement without curved brackets c++
@LordHonkInc
I like Allman as a general rule because it affords both the condition and the action to be expanded and visually blocked out. Like, sure, "if (x==y) return;" can be a one-liner, but in a larger example:
"if(x < 0 || x > width ||
y < 0 || y > height)
{
printf("Object out of bounds at %i %i\n",x,y);
free(pObj);
}"
@BearWithHands
Allman has always been the team standard I've had
@indoorstayer
standard on top you can't argue
@cyrilshestakov3623
The one that is referred to as "standard" is actually The Kernighan & Ritchie (K&R) style sometimes also called egyptian brackets
@tonhauer
Ternary if's are the best
@cirkulx
i am very guilty of mixing both standard and single liner including single line if else with just an indentation if its too long, i think it looks clean personally
@mechaboy95
my favorite is
if (not condition) {
doNothing }
doSomething
@justfeeldbyrne2791
Allman all the way. It helps me read it better, idc if it adds useless lines where they dont need to be, trust me when i say it makes reading 17 nested if statements a whole lot easier.
@CodingWithLewis
Team standard
@trumpetbob15
Yeah, I'm the Allman style camp for the most part, but will use single-liners for a test/return statement. (Probably should also admit to being lazy and occasionally doing the split single-liner where the if is on one line and the result is indented below it without using brackets. Inevitably though, I end up adding a second thing to happen, and then have to go back and add the brackets to become Allman style again.)
@Quxer0721
For me what I consider good examples: 1. single liner for returns to avoid multiple nesting statements and unnecessary elses, but with short condition 2. two liner, when you have similar situation with single liner, but you need to invoke single method without returning or you have long condition and return 3. allman for every multiple liners, easier for me to read and better looking, when you have multi line condition.
@fbiagentmiyakohoshino8223
im allman and single liner for logic that is all done on a single lone (saves space) also allman on top 😎
@re.liable
my current preference is, - when returning/yielding something (even null), use standard, which is almost always the case - otherwise when the expression is empty, e.g. continue/break, can use single-line. but even then i still tend to use standard to keep things uniform
@HaramGuys
I like Allman cuz its easy to tell where a block begins and ends
@gJonii
I'm a fan of Python, but Allman style makes me want to program in a language with brackets. It's extremely clean and nice. Takes a slight bit of extra space Python avoids, but it allows also more complicated conditions to be immediately obvious which Python struggles with more.
@MechMK1