From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vdavydov.dev@gmail.com>
Date: Tue, 30 Apr 2019 15:50:52 +0300
From: Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [PATCH v3 3/7] lua: optimize creation of a tuple from a tuple
Message-ID: <20190430125052.cxxu4kkphpg7lz5x@esperanza>
References: <cover.1554906327.git.alexander.turenko@tarantool.org>
 <eb8d159b6f049306a12d160e4cd334ce77ed4a14.1554906327.git.alexander.turenko@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <eb8d159b6f049306a12d160e4cd334ce77ed4a14.1554906327.git.alexander.turenko@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@freelists.org
List-ID: <tarantool-patches.dev.tarantool.org>

On Wed, Apr 10, 2019 at 06:21:21PM +0300, Alexander Turenko wrote:
> Don't parse tuple data, just copy it.

I don't understand: luamp_encode_tuple doesn't parse or decode a tuple.
It simply copies it to the stream. This patch simply eliminates an extra
memcpy, right?

Is this small optimization worth complicating the code?