unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
* RFC: drop notmuch_private_status_t, or use it better?
@ 2022-05-23 10:18 David Bremner
  0 siblings, 0 replies; only message in thread
From: David Bremner @ 2022-05-23 10:18 UTC (permalink / raw)
  To: notmuch


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?

d

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-05-23 10:18 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-23 10:18 RFC: drop notmuch_private_status_t, or use it better? David Bremner

Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).