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 _______________________________________________ notmuch mailing list -- email@example.com To unsubscribe send an email to notmuch-le...@notmuchmail.org