>
> I think this is a good general principle for *raising standards* in the
> codebase like this: if somebody says something is important, and cannot be
> convinced otherwise, then it should generally be treated as important. This
> is different from cases where there are simply competing approaches.
>


FTR this is my preference too.  The code trends in one direction, there's
no ambiguity or conflict when in doubt.  And IMHO the simple rule is to
what is hot path is whether it's called more than once per request.  It's
not close to accurate, but it's such an easy line to draw (and one which
tests fall into).

Reply via email to