On Sat 04 Jul 2020 at 14:17 -0300, David Bremner wrote: > Floris Bruynooghe <f...@devork.be> writes: > > >>> - * This function will not return NULL since Notmuch ensures that every >>> - * message has a unique message ID, (Notmuch will generate an ID for a >>> - * message if the original file does not contain one). >>> + * This function will return NULL if triggers an unhandled Xapian >>> + * exception. > >> How much of a departure from the existing API is this? Will this be >> possible with all functions? I had a quick look and tried some other >> functions that don't return notmuch_status_t: > > It's upward compatible in that any code which crashes because it was not > expecting a NULL pointer, will already be crashing in the same > circumstances because of an uncaught exception / call to abort.
Oh yes, that is a very good point. This choice seems very reason then. Cheers, Floris _______________________________________________ notmuch mailing list -- email@example.com To unsubscribe send an email to notmuch-le...@notmuchmail.org