Re: [PATCH COMMITTED] src: Fix NDEBUG compilation: avoid side-effects in assert

[Jose E. Marchesi]

    on a related note: how about re-defining `assert` to `(void)(cond)` for
    NDEBUG builds, so that we don't get a plethora of unused variable
    warnings now?

Hm, is that common practice?  It seems to me that if a given variable is
only used in an assert, we probably want to identify it so we can
rewrite the code to avoid that situation.
    
    Also, are NDEBUG builds actually a good idea? I recall that when fuzzing
    poke a lot of "crashes" that I found were just failed assertions. So
    maybe we should refrain from supporting NDEBUG builds for now?

Well, we are not "supporting" NDEBUG, meaning no build mode of poke
AC_DEFINEs NDEBUG.