The Vale Programming Language
Interesting to read about variable mutability here:<p><a href="https://verdagon.dev/blog/on-removing-let-let-mut" rel="nofollow">https://verdagon.dev/blog/on-removing-let-let-mut</a><p>Originally there was <i>let</i> and <i>let mut</i> like Rust. But that was changed to simple assignments, followed by the compiler checking for subsequent reassignment with <i>set</i>.<p>While I can see that might make for cleaner code while still allowing the compiler to get on with its job, surely one of the benefits of explicitly immutability is to stop the coder accidentally letting off foot guns. If simply setting a variable after declaration makes it mutable, it feels like it could open the door to data in a code block being allowed to change behind the scenes when the assumption in that block is that it is fixed.<p>I'd be interested to know how this works in every day practice and possible unintended effects.