From: Trevor Jim <tjim@mac.com>
To: David Bremner <david@tethera.net>,
Tomi Ollila <tomi.ollila@iki.fi>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] go: add binding for notmuch_message_get_date
Date: Tue, 03 Mar 2015 11:22:54 -0500 [thread overview]
Message-ID: <m261aijbj5.fsf@att.com> (raw)
In-Reply-To: <87385mmasu.fsf@maritornes.cs.unb.ca>
> Given the current troubles with the main library API and missing status
> values, I'd say in the long run we'll be happier with a real status
> return. OTOH, I don't much about go.
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?
In defense of the current strategy, any caller can check for the nil
case before calling.
-T
next prev parent reply other threads:[~2015-03-03 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 20:39 [PATCH] go: add binding for notmuch_message_get_date Trevor Jim
2015-03-03 12:32 ` Tomi Ollila
2015-03-03 14:10 ` David Bremner
2015-03-03 16:22 ` Trevor Jim [this message]
2015-03-06 7:20 ` David Bremner
2015-03-03 16:39 ` Trevor Jim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m261aijbj5.fsf@att.com \
--to=tjim@mac.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).