3 ms·
You really don’t get most of the benefits “Strongly typed” languages here. A program that fails with type errors at runtime instead of compile time is the worst
by donatj 7y ago
You really don’t get most of the benefits “Strongly typed” languages here. A program that fails with type errors at runtime instead of compile time is the worst of all worlds.
- tyingq 7y agoContinuing to run with unexpected type coercion bugs could be worse than bailing out. So, worse than compile time checking, yes. But not the worst.
- tuesdayrain 7y agoIt just seems to imply that you need input validation code regardless of how your language is typed.
- Ididntdothis 7y agoThis will help you find type errors if you have good test coverage without explicitly testing for types. Makes tests shorter.
- TazeTSchnitzel 7y agoYou can use third-party tools to check ahead of time, and you can fall back on the PHP runtime to catch what can't be caught in advance.
- nicoburns 7y ago> A program that fails with type errors at runtime instead of compile time is the worst of all worlds Better than silently failing! + if code fails early as these type checks can enable, then bugs are often (not always) picked up just by running the code once.