1 Return-Path: <dkg@fifthhorseman.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by arlo.cworth.org (Postfix) with ESMTP id CA1276DE0B2F
\r
6 for <notmuch@notmuchmail.org>; Mon, 7 Dec 2015 14:54:25 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=-0.090]
\r
13 Received: from arlo.cworth.org ([127.0.0.1])
\r
14 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id b50NWogGh1Tz for <notmuch@notmuchmail.org>;
\r
16 Mon, 7 Dec 2015 14:54:24 -0800 (PST)
\r
17 Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])
\r
18 by arlo.cworth.org (Postfix) with ESMTP id 0C3486DE0B29
\r
19 for <notmuch@notmuchmail.org>; Mon, 7 Dec 2015 14:54:23 -0800 (PST)
\r
20 Received: from fifthhorseman.net (ool-6c3a0662.static.optonline.net
\r
22 by che.mayfirst.org (Postfix) with ESMTPSA id 6066FF984
\r
23 for <notmuch@notmuchmail.org>; Mon, 7 Dec 2015 17:54:22 -0500 (EST)
\r
24 Received: by fifthhorseman.net (Postfix, from userid 1000)
\r
25 id 7B83F1FF49; Mon, 7 Dec 2015 17:54:21 -0500 (EST)
\r
26 From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
\r
27 To: notmuch mailing list <notmuch@notmuchmail.org>
\r
28 Subject: NOTMUCH_STATUS_LAST_STATUS problematic across additive library
\r
30 User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1
\r
31 (x86_64-pc-linux-gnu)
\r
32 Date: Mon, 07 Dec 2015 17:54:21 -0500
\r
33 Message-ID: <87y4d5q38i.fsf@alice.fifthhorseman.net>
\r
35 Content-Type: text/plain
\r
36 X-BeenThere: notmuch@notmuchmail.org
\r
37 X-Mailman-Version: 2.1.20
\r
39 List-Id: "Use and development of the notmuch mail system."
\r
40 <notmuch.notmuchmail.org>
\r
41 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
42 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
43 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
44 List-Post: <mailto:notmuch@notmuchmail.org>
\r
45 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
46 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
48 X-List-Received-Date: Mon, 07 Dec 2015 22:54:25 -0000
\r
52 notmuch_status_t is an enum that counts up to
\r
53 NOTMUCH_STATUS_LAST_STATUS.
\r
55 This is fine for work within the library itself, but it seems
\r
56 problematic to expose it to users of the library.
\r
58 In particular, if a user builds against version X of the library, then
\r
59 version X+1 is released with a new status code (but no
\r
60 backward-incompatible API/ABI changes that would require an SONAME
\r
61 bump), then the value of NOTMUCH_STATUS_LAST_STATUS would change, but
\r
62 the application using notmuch wouldn't know about it.
\r
64 Is this something we should be concerned about? I don't know why or
\r
65 when a library user might try to make use of NOTMUCH_STATUS_LAST_STATUS,
\r
66 but it's also exposed in the go bindings, so it's leaking out quite a
\r