3 ms·
If you can check in those problems, and make them problems for everyone else - it absolutely is an issue! If the policy is ‘you can generate “warnings” all you
by lazide 4y ago
If you can check in those problems, and make them problems for everyone else - it absolutely is an issue!
If the policy is ‘you can generate “warnings” all your want locally, but you can’t check them in’ then sure.
The issue of course is folks want to check things in as soon as they ‘work’ in their basic use case, even if it means bypassing a bypassable alert.
So it means enforcing it at check-in time, in a non bypassable way (usually), which just means folks have a lot of ‘hidden’ cleanup to do before submitting, while they have their code ‘working’, which is always a drag.
- hbrn 4y agoSuch policies should be defined by the company, not enforced by the language. Even in static languages world, a lot of projects allow dev/nightly builds to be unstable. Which is literally what you're talking about: checking in problems for everyone else. But checking in policy is a VCS/CI domain, not a language domain.
- lisper 4y agoAnd what is to prevent someone from checking in code that doesn't compile?