Unpopular opinion, but I like writing Rust code in camelCase.
I came from Java, so it kind of makes sense.
I'm glad the Rust devs thought to allow disabling non-snake_case warnings.
This language is actually really great and versatile. (I also use tabs instead of spaces)
15 replies
Sorry, but we'll have to
cargo clippy --fixyouYour editor automatically converts tabs into spaces, right?
... right?
Nope! I make sure set it to tabs only!
🔥 burn the heretic 🔥
[insert Linus' rant]
So only indentation, no alignment then?
Wait hold up I thought that yours was converting spaces into tabs?
java was my first language and now every time i changed contracts from java to something else like python, or ruby, or c++, i still keep using camelcase out of habit and it drives the other devs mad. fortunately, i mostly refactor legacy work so i almost never work on new stuff that would let me use camelcase. lol
You like, but you shouldn't: there are conventions we should respect as a community.
I like to program using sarcastic spongebob case. Gives me more time to think, the variables and functions look different to other library methods.
Tabs > spaces for sure, but camel case is blasphemy.
I do like the idea of having an intent level character. And once we have that, we don't need AltGr7 etc (curly braces) to denote which level we're at either, the whitespace has all the information we need.
But ultimately I just use whatever is default for the language formatter these days. My own personal preferences on that isn't actually that important, and I find that's a common feeling once someone just works with the default for a while.
I feel like the downfall of such an indent-level character is that it's whitespace. If it was somehow visible by default, you'd run into a lot less situations where folks accidentally add spaces-indentation into a tabs-only codebase and it would also help make indentation changes properly visible.
Last week, I had to look at an Ansible codebase (i.e. YAML), where a colleague had introduced a
block:statement, where then everything indented below that will have its errors caught. It took me about a minute to understand how the hell this construct works, because I did not see that the deeper indentation had stopped at some point. That's just a waste of time for no good reason.To be fair whoever invented YAML was just a sadist in general who wanted to see everyone in the industry suffer.
Ahh, one fewer key to hit, mi amigo!
It doesn't look as "computer nerdy" as snake case, but I also prefer the readability of it.