4 ms·
Rust could just have mandated that const have to be uppercase and disallowed variables starting with uppercase. It would be better than making a warning.
by RandomThoughts3 2y ago
Rust could just have mandated that const have to be uppercase and disallowed variables starting with uppercase. It would be better than making a warning.
- eviks 2y agoNo it wouldn't, it's just too unergonomic of a style to force upon everyone
- RandomThoughts3 2y agoHow is that unergonomic? Go has proven at this point that the language spec is the correct place to settle stupid bike sheding especially when they lead to misfeature like this one. I understand that it’s not the most urgent thing to fix when it comes to Rust syntax but still a clear downside.
- eviks 2y agoYou have to hold an inconvenient key while typing. And you can't assess its stupidity if you can't even understand this simple why on your own
- RandomThoughts3 2y agoI mean if your why is related to having to hold shift or - gasp - using caps lock, I don’t know if I can’t assess the stupidity but I certainly don’t feel I’m clever enough to hold a conversation with you.
- estebank 2y agoIf you care about this rule, you can deny it on your projects (at the crate level or for individual items), but if it were an unconditional error then it would make things like FFI or following non-Rust naming conventions either annoying or impossible.
- RandomThoughts3 2y ago> following non-Rust naming conventions […] impossible. That’s indeed the point.