It may not be possible for us to ever reach empirical definitions of "good code" or "clean code", which means that any one person's opinion about another person's opinions about "clean code" are necessarily highly subjective. I cannot review Robert C. Martin's 2008 book Clean Cod...
I’m probably preaching to the choir on here when I bring Rust into this, but yeah, reading this kind of article makes me appreciate Rust’s explicitness even more.
Rather than everyone having to keep to best practices, to not modify arguments, the language simply requires you to specify, if you want to modify an argument and your caller also has to opt into that.
When I started out with Rust, I was worried that this would be too much detail work, but given that it’s usually a bad practice to modify arguments anyways, yeah, this actually works out really well.