3 ms·
This is an academic definition. In a system with dependencies, if you change behavior your dependents relied on, you broke them. If you didn't, you didn't. In
by camgunz 3y ago
This is an academic definition. In a system with dependencies, if you change behavior your dependents relied on, you broke them. If you didn't, you didn't.
In other words, if you break prod, "but we never promised to behave this way" is a poor excuse. When changing something, it's your responsibility to check for breakage, not just throw up your hands and say "not our fault" if it occurs.
- kazinator 3y agoE.g. a number of years ago now someone in Glibc development thought it would be fine to change the behavior of memcpy for overlapping objects. Nobody does that, right? It's undefined behavior. Downstream distros broke; it had to be backpedaled out.