I feel like your point is strong, but I've never known a dev to miss the distinction between mutable vs const name binding.
In rust that kind of change is a public API-breaking change so people are more intentional about it.
-
-
I really want const to mean "the author thought this variable shouldn't be mutated" not "it happened to not be mutated".
-
I can tell the latter by looking at the code. The former is lost forever.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.