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. -Carl