4 ms·
> Yes, policy debates are amazing, so fun, so productive. Who says there's going to be a debate? The commit hooks and/or CI pipeline should prevent you from m
by lliamander 4y ago
> Yes, policy debates are amazing, so fun, so productive.
Who says there's going to be a debate? The commit hooks and/or CI pipeline should prevent you from merging code that doesn't pass typecheck. It's still enforced by tooling, just at a different place in the process.
- lazide 4y agoWhich lets folks get deeper into trouble before running into a wall.
- lliamander 4y agoWell, you're going to want those checks regardless because, if we really want to be pessimistic, developers can commit code without running the compiler locally anyway. The question is really, before you commit/push your code, and you just want to run the code, do you really need to be prevented from running the code just because it didn't pass typecheck? I'm inclined to say no.
- lazide 4y agoIt’s not being pessimistic, it happens all the time, which is why CI/CD is a thing. It’s also why if it’s a compiled language, I’d personally want to know if it’s definitely not going to be working if I go to check it in right away. If I wanted something that could kinda work, I’d just use a scripting language?