๐ป๐ผ๐๐๐๐๐โcodeStyle
forcesnake case for everything, pascal case for struct/enum names, and upper snake case for constexpr identifiers is the superior method of naming. FUCK camel case
Preach! C# apologists with their pascal case use are an evil we must conquer.
screaming snake case
What a great name for that style. Thank you.
Apart from screaming case, which is for textual macros, i approve.
One advantage of snake case is never having to remember which letters of every acronym or compound word the author decided to capitalize.
xigoiI just like to treat acronyms/initialisms as normal words.
sendHttpRequest, etc.
MesaThis is the way.
You already donโt have to do that. Thatโs what IDEโs have autocomplete for.
That viewpoint makes bold assumptions about language, toolset, and preference.
It also suggests sweeping the dirt under the rug instead of not having it on the floor in the first place.
I hate that the convention for naming React.useState variables is [color, setColor], rather than [color, colorSet]. After I declare โcolorโ, I want to copy/paste that variable and append โSetโ, rather than copy the variable then writing โsetโ then pasting then navigating to the 4th character then flipping the case.
Granted there could be some ambiguity if there was a variable containing a unique collection (aka set) but that is far less common than declaring a useState variable. Iโd even settle for appending โSETโ to quell the confusion.
publ;c class customer_data {