From: Stefan Beller <sbeller@google.com>
Date: Wed, 22 Nov 2017 23:08:00 GMT
Subject: Re: [PATCH 1/3] Documentation/CodingGuidelines: explain why assert is bad
Message-ID: <CAGZ79kY7yrgYSM7jLQD3Q4sRpjovXY=HZwU4M-Ai_XRPseda9A@mail.gmail.com>
In-Reply-To: <20171122225913.GF11671@aiede.mtv.corp.google.com>

On Wed, Nov 22, 2017 at 2:59 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:

> In a certain ideal world, the preference would be reversed: you'd want
> to use assert() wherever you can and require the compiler to check
> that all assert()s are verifiable at compile time.  A check that a
> static analyzer can verify is more valuable than a run-time check.
> When a compile-time check is not possible, you'd have to fall back to
> BUG_ON().

Linux has BUILT_BUG_ON as well, which we may desire?