Benjamin Coutu <[email protected]> writes:
> That got me thinking: some projects (like PHP) map the ASSERT macro to ASSUME
> in non-assert builds. The rationale is that ASSERT typically expresses a
> tautology, something the programmer believes to be always true. So in builds
> where assertions are compiled out, we can still pass that information to the
> optimizer via ASSUME.
My gut instinct is that this would not help much; we don't typically
write assertions that would help the compiler all that much. And
in any case, to my mind there is a considerable difference in goals
between Assert and Assume, which I'd prefer not to fuzz like this.
regards, tom lane
