From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: kostja.osipov@gmail.com
Cc: tarantool-patches@freelists.org
Subject: Re: [PATCH] Drop const qualifier of struct tuple
Date: Fri, 5 Apr 2019 14:46:28 +0300 [thread overview]
Message-ID: <20190405114628.ah3upqd5yopc5pcg@esperanza> (raw)
In-Reply-To: <b33b31d1fe6678064247c93a93ca71ce980b965a.1554460860.git.vdavydov.dev@gmail.com>
On Fri, Apr 05, 2019 at 02:31:06PM +0300, Vladimir Davydov wrote:
> Using the const qualifier for complex structures like tuple is bad.
> We already have to cast it to drop the const qualifier now and then,
> e.g. to increment/decrement the reference counter.
>
> We are planning to wrap struct tuple in a helper struct (aka entry) to
> store it in vinyl containers along with a comparison hint (cache, memory
> tree, etc). We will be passing this struct by value so we won't be able
> to retain const qualifier, because in contrast to a const pointer, one
> must initialize a const struct upon definition.
>
> That said, it's time to drop const qualifier of struct tuple everywhere,
> like we have already done in case of struct key_def and tuple_format.
Kostja approved verbally. Pushed to master.
prev parent reply other threads:[~2019-04-05 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 11:31 Vladimir Davydov
2019-04-05 11:46 ` Vladimir Davydov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190405114628.ah3upqd5yopc5pcg@esperanza \
--to=vdavydov.dev@gmail.com \
--cc=kostja.osipov@gmail.com \
--cc=tarantool-patches@freelists.org \
--subject='Re: [PATCH] Drop const qualifier of struct tuple' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox