RFC: drop notmuch_private_status_t, or use it better?

Subject: RFC: drop notmuch_private_status_t, or use it better?

Date: Mon, 23 May 2022 07:18:07 -0300

To: notmuch@notmuchmail.org


From: David Bremner

This is probably mostly my fault, but we have not really taken advantage
of having a private set of status values, and defined only one private
status value since 2010. Currently they are mainly a source of extra
code (to coerce return values) and potential for error (if / when they
get out of sync with the public status values. It occured to me we could
relatively easily just drop them (adding 3 status values to the public
values).  It is true that these three status values would probably never
reach user code; I'm just wondering if the simplification of the
library would be worth it. Alternatively are we missing an opportunity
in the library to add more private status codes and make the code
somehow more robust or maintainable?


notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org