On Tue 2015-12-08 00:22:11 -0500, Carl Worth wrote: > On Mon, Dec 07 2015, Daniel Kahn Gillmor wrote: >> I note that it's exposed in the go bindings -- maybe it shouldn't be >> exposed in any of the bindings that can avoid exposing it? > > Quite likely. It's only there in C because there's no other way to know > the bounds for iterating over all possible values for a particular > enum. If other languages don't have this deficiency, then they shouldn't > need this silly thing. OK, so maybe the following patch should be applied. Perhaps someone who understands the go bindings better than i do can comment on it? The python bindings don't seem to include LAST_STATUS, so i think they're OK. --dkg diff --git a/bindings/go/src/notmuch/notmuch.go b/bindings/go/src/notmuch/notmuch.go index 0fff1ab..9f910cb 100644 --- a/bindings/go/src/notmuch/notmuch.go +++ b/bindings/go/src/notmuch/notmuch.go @@ -28,8 +28,6 @@ const ( STATUS_TAG_TOO_LONG STATUS_UNBALANCED_FREEZE_THAW STATUS_UNBALANCED_ATOMIC - - STATUS_LAST_STATUS ) func (self Status) String() string {