Trevor Jim <tjim@mac.com> writes: > I'm not sure what the "current troubles" are (happy to hear more), but > the way I've handled the nil case is in keeping with the way it's > handled in the other function bindings for go. Adding an error return > to all relevant functions seems like a big change that should be handled > separately, yes? It seems like at least some functions [1] already use multiple return values to return a status value. There is also already a STATUS_NULL_POINTER defined. [1]: from notmuch.go func NewDatabase(path string) (*Database, Status) { func OpenDatabase(path string, mode DatabaseMode) (*Database, Status) { func (self *Database) Close() Status { func (self *Database) GetDirectory(path string) (*Directory, Status) { func (self *Database) AddMessage(fname string) (*Message, Status) { func (self *Database) RemoveMessage(fname string) Status { func (self *Database) FindMessage(message_id string) (*Message, Status) { func (self *Message) AddTag(tag string) Status { func (self *Message) RemoveTag(tag string) Status { func (self *Message) RemoveAllTags() Status { func (self *Message) Freeze() Status { func (self *Message) Thaw() Status {