The issue that I’m primarily talking about is not so much in the way that errors are handled, it’s more about the way of deciding what constitutes an exception to a general rule, as Google defines the word “exception”:
a person or thing that is excluded from a general statement or does not follow a rule.
In other words, does everything need a rule to be applied to it? Does every rule need there to be some set of objects under which the rule is applied that lie on one side of the rule rather than the other (namely, the smaller side)?
As soon as we step outside of binary rules, we are in Case-when-land where each category of objects is treated with a part of the automation that is expected to continue. There is no longer a “does not follow” sense of the rule. The negation there is the part doing the work that I take issue with.
The issue that I’m primarily talking about is not so much in the way that errors are handled, it’s more about the way of deciding what constitutes an exception to a general rule, as Google defines the word “exception”:
In other words, does everything need a rule to be applied to it? Does every rule need there to be some set of objects under which the rule is applied that lie on one side of the rule rather than the other (namely, the smaller side)?
As soon as we step outside of binary rules, we are in Case-when-land where each category of objects is treated with a part of the automation that is expected to continue. There is no longer a “does not follow” sense of the rule. The negation there is the part doing the work that I take issue with.
Exceptions in programming aren’t “exceptions to a rule” , they are “potential problems”.
I really don’t think I can accept this objection. They are clearly considered both of these, most of the time.
I would really prefer that if you really want to find something to have a problem with, first it’s got to be true, then it’s got to be meaningful.