codeStyle
codeStyle
You're viewing a single thread.
44 comments
-
Don't look at rust code
-
I think Rust actually is actually among the best in this regard for the simple reason that there is consistency given by the compiler. A simple
cargo fmtandcargo buildwill fix or warn you about everything. I can read into Rust codebases so quickly. C++ was always really exhausting because most of the time you were just getting used to the code style. -
Why? It's fine?
-
I've found whenever people complain about rust code they can only point out how it's different but not why it's worse and I can usually point to a reason why it's better.
to be fair, I get sometimes it's difficult to pinpoint why something is bad and even "being different" can be a legitimate criticism on its own
-
People who learnt structural OOP without actually understanding typing system and their benefits really struggle with learning Rist as they try to map classes onto structs and it just doesn’t work.
Traits are not inheritance.
Boxis not polymorphism. Rust is not C++ with more keywords.
-
-
It IS fine, I though the comic was referring snake_case as disgusting. I was uncomfortable too at first but I got used to it
-
I used to be a PascalCase guy myself, but that changed recently when I had to use React (coming from embbeded C)
I am working with a C embedded framework that uses snake_case, and switching between the two, I realized that it is a lot easier to find information with snake_case for me.
-
-
-
I don't get why every language seems to have its own coding style when you'd think they'd be completely interchangeable depending on user/org/project maintainer preference
-
Having a standardized codding styles allows people to immediately recognise things, and not have a wacky case mix.
You don't need to remember the coding style of one specific project. You just need to remember the style of the language
Of course it would be better if it was standardized for every language, but that's probably never going to happen
-
-
44 comments