From: David Bremner <david@tethera.net>
To: Dirk Van Haerenborgh <vhdirk@gmail.com>
Cc: notmuch@notmuchmail.org, Carl Worth <cworth@cworth.org>
Subject: Re: Pointer ownership
Date: Sat, 22 Dec 2018 15:11:30 +0900 [thread overview]
Message-ID: <87zhsyytt9.fsf@tethera.net> (raw)
In-Reply-To: <CAHQqoqNs3gpjkEqHR3Vao70UGN3LnTU+KNzLE40fJvvwX1ff+A@mail.gmail.com>
Dirk Van Haerenborgh <vhdirk@gmail.com> writes:
> Thanks.
>
> For the most part, that's what I ended up with, but the thread 'stealing' a
> message will be quite hard to implement in Rust, I guess.
> When using notmuch_query_search_messages, I was assuming the resulting
> individual messages to be owned by the query.
> So, if at a later point in time, one uses notmuch_query_search_threads,
> will the ownership of a previous message abruptly be
> transferred from query to thread?
> I do want to be able to run *_destroy at some point :)
It's still (transitively) owned by the query in that case, since the
threads are owned by the query.
d
next prev parent reply other threads:[~2018-12-22 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 7:42 Pointer ownership Dirk Van Haerenborgh
2018-12-16 23:22 ` David Bremner
2018-12-20 9:21 ` Dirk Van Haerenborgh
2018-12-22 6:11 ` David Bremner [this message]
2018-12-23 10:04 ` rhn
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=87zhsyytt9.fsf@tethera.net \
--to=david@tethera.net \
--cc=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=vhdirk@gmail.com \
/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).