A program that compiles in Haskell can still break, consider:
main = do
print $ head []I can't see any reasonable definition of "break" for this context for which that is valid; its exactly the same kind of breakage that strong type checking reduces the incidence of in Haskell compared to dynamic languages -- runtime errors resulting from a function call not being able to complete without error for all inputs that the language will allow to be passed to it.
> Taking the head of an empty list is no more a break than dividing something by zero.
I agree; both are clearly examples of things that can cause a program to break.
So just compile and ship; no testing?
What's the longest you've maintained something?
So I don't think your observation answers the GP's point at all.
There was some computation which produced a wrong result, which was detected, handled and diagnosed.
In what development tool does this never happen?