On Wed, Sep 30, 2020 at 4:54 AM Jeff King <peff@xxxxxxxx> wrote: > I'm a little nervous that the second "wart" may actually be making > things worse, because now we sometimes produce a wrong answer and > sometime a right one, and it can be difficult to know which options > cause which (e.g., rename detection puts us onto the slow path). Is it > worse to sometimes be right and sometimes wrong, or to always be > consistently and predictably wrong? I suppose one could even argue that > the current semantics aren't "wrong", but just what we happen to > produce. But IMHO they are so un-useful as to be considered wrong. "Predictably wrong" *is* actually useful while "unpredictably wrong" is, um, "less useful". Perhaps just documenting exactly which options use which path? Basically turn some of this into documentation. Chris
