From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: RFC: drop notmuch_private_status_t, or use it better?
Date: Mon, 23 May 2022 07:18:07 -0300 [thread overview]
Message-ID: <87wnec8sdc.fsf@tethera.net> (raw)
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
reply other threads:[~2022-05-23 10:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnec8sdc.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).