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.
If 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.
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.
I 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.