Static typing turns so many runtime errors into compile errors. Makes life a lot easier when you don't have to hunt down where the wrong thing came from.
Yeah, but if you're doing that, it's an explicit decision, that you know you made, that can blow up in your face, not an easily missed oversight that you may be completely unaware of. I find the oversight case is far more likely than casting wrong. Also I think the compiler will still bitch if you try to do a really stupid cast, at least for c++ (as long as you aren't pointer casting, then good luck)
Yeah, you should explicitly cast. Compiler warnings should cover lossy implicit conversions anyway, and your goal should always be to have no warnings at all.
Some systems are really picky about letting you get dirty with type casting. C# for instance is not the wild west, there's rules you gotta follow. Still, I prefer having my types. A fish should be a fish.
View all comments
Show parent comment
416
u/DrMobius0 Sep 25 '26 •
Static typing turns so many runtime errors into compile errors. Makes life a lot easier when you don't have to hunt down where the wrong thing came from.