From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp32.i.mail.ru (smtp32.i.mail.ru [94.100.177.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id DE6A6469719 for ; Tue, 29 Sep 2020 08:03:28 +0300 (MSK) Date: Tue, 29 Sep 2020 08:03:40 +0300 From: Alexander Turenko Message-ID: <20200929050340.hwglcb2s4yyadcjr@tkn_work_nb> References: <578d97ed-92a0-0154-a244-f94c36f32873@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <578d97ed-92a0-0154-a244-f94c36f32873@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 2.X 2/7] module api: export box_key_def_dup List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org On Tue, Sep 29, 2020 at 12:21:02AM +0200, Vladislav Shpilevoy wrote: > Thanks for the patch! > > See 2 comments below. > > On 24.09.2020 19:00, Timur Safin wrote: > > Exporting `box_key_def_dup` as accessor to the internal `key_def_dup` > > 1. Do you really need this method? It looks like it can be done by > > old_parts = box_key_def_dump_parts(old_key_def); > new_key_def = box_key_def_new_ex(old_parts); > > So the method seems redundant. It is not strictly necessary, however using of box_key_def_dup() would be less error-prone (no extra allocations) and the resulting code would be more readable. My vote is for this method if you have no strict objections.