Re: assert vs BUG [was: [PATCH v1 05/10] cat-file: use delta_base_cache entries directly]
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 19, 2024, 15:50 UTC
- Message-ID
- <xmqqr0akfr5a.fsf@gitster.g>
- In-Reply-To
- <20240818173637.M96307@dcvr>
Eric Wong <e@80x24.org> writes:
Show 10 quoted lines
> Eric Wong <e@80x24.org> wrote: >> Patrick Steinhardt <ps@pks.im> wrote: >> > We shouldn't use asserts, but rather use `BUG()` statements in our >> > codebase. `assert()`s don't help users that run production builds. >> >> OK. > > Thinking about this more, I still favor assert() in common code > paths since it's only meant to be used during development and > later removed or neutralized (via -DNDEBUG).
I have a mixed feeling.
I agree that assert() is only meant to be used during development, but we only want code that is polished enough to be added to the system, so there is no place for assert() in the code in 'master'.
The point of BUG() is that it is not easily "neutralized", so it can help safeguarding the production code from harming the end-user data due to doing nonsense things without noticing that the precondition is not satisfied for it to perform correctly. It makes sense to have it in both during development and after deployment.