3 ms·

> And you might want to figure such things out, [...] before you go around telling people they're wrong on the internet Apply it to yourself my friend, you are

by kolme 6y ago

> And you might want to figure such things out, [...] before you go around telling people they're wrong on the internet Apply it to yourself my friend, you are wrong again. What you are talking about here is implicit type coercion, which doesn't have much to do with strong vs weak types. Also in your example you do get a warning, so it doesn't seem to be a problem?

darksaints 6y ago
Implicit type coercion is exactly the difference between strong and weak types. FFS. https://www.educative.io/edpresso/statically-v-dynamically-v-strongly-v-weakly-typed-languages https://www.educative.io/edpresso/statically-v-dynamically-v... And if you really do not believe that to be a problem because the compiler warned you about it, I bid you the best of luck. You're gonna need it. There are dozens of ways that bug can sneak its way past the compiler where you won't get a warning because the compiler only does local type inference.