"If you can do them at compile time, performance isn't affected at all and the code won't run slower."
That's not universally true. Compiler people tell me some optimizations happen using undefined behavior. Personal experience shows some, esp hand-optimized assembly, rely on stuff that a static analyzer just couldn't handle. These are common in compression, encryption, and multimedia libraries. So, you indeed might sacrifice performance writing code in a language that can knock out all kinds of problems at compile time working within the coding style it needs to do that.
In the general case, though, your point holds so far as lots of problems can be knocked out at compile time without affecting performance enough for the user to care.
Comments
"If you can do them at compile time, performance isn't affected at all and the code won't run slower."
That's not universally true. Compiler people tell me some optimizations happen using undefined behavior. Personal experience shows some, esp hand-optimized assembly, rely on stuff that a static analyzer just couldn't handle. These are common in compression, encryption, and multimedia libraries. So, you indeed might sacrifice performance writing code in a language that can knock out all kinds of problems at compile time working within the coding style it needs to do that.
In the general case, though, your point holds so far as lots of problems can be knocked out at compile time without affecting performance enough for the user to care.