Always use braces

[cmcculloh-kr]

I'm OK with saying that people can omit braces in a unique particular instance if they want, but, I am extremely uncomfortable dictating that they must not use braces in some subjective instances. I find it an acceptable evil to ommit braces in some cases if you really want, but, would rather the consistency of just saying "always use braces".

[interactivellama]

Sounds good to me.

[swilliamset]

+1 I believe many of these suggestions/guidelines/standards need to be more in the spirit of consistency.

Next question does each bracket get its own line? If not is there a space before/after the bracket? So many options ;)

[cmcculloh-kr]

+1 on the "spirit of consistency" thing. As a college professor of mine always said, "It doesn't so much matter what you choose, but that you choose something and stay consistent"

You might be trolling about C style bracketing, but, just in case you aren't, I prefer exactly what is (now) lain out in the spec. ie. That the initial bracket is on the line that needs it and the closing bracket is on it's own line:

if() {
    //doo dad
}

The reason for this is that:

if ()
{
    //doo dad
}
else
{
    //doo did
}

Both wastes space and is actively dangerous. It would be all too easy for someone not paying attention to accidentally make it:

if ()
{
    //doo dad
}

//moar code (didn't notice the `else`)

else
{
    //doo did
}

[kevinparkerson]

So long as I can do this:

if(1===1){
    //do thangs
}

I'm happy. I like my characters riding all up on each other, the extra spaces are unnecessary and ugly IMO

[cmcculloh-kr]

You can write it that way, but, if you use the esformatter definition that (either is, or will shortly be) is in this project, it will auto-convert it to this:

    if (1 === 1) {

    }

[cmcculloh-kr]

If you don't use the esformatter, no worries, but, when someone else does and they save the file, it will convert it at that point.