NOTMUCH_STATUS_LAST_STATUS problematic across additive library upgrades

[Carl Worth]

On Mon, Dec 07 2015, Daniel Kahn Gillmor wrote:
> In particular, if a user builds against version X of the library, then
> version X+1 is released with a new status code (but no
> backward-incompatible API/ABI changes that would require an SONAME
> bump), then the value of NOTMUCH_STATUS_LAST_STATUS would change, but
> the application using notmuch wouldn't know about it.

Can you envision a scenario where this would actually lead to a bug?

It's meant to provide a convenience. It's clearly documented as "not an
actual status value", so, yes, no client code should ever be passing
that value into the library.

-Carl

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20151207/f0226f34/attachment.sig>