From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp48.i.mail.ru (smtp48.i.mail.ru [94.100.177.108]) (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 05EFB469719 for ; Tue, 13 Oct 2020 03:46:13 +0300 (MSK) Date: Tue, 13 Oct 2020 03:46:32 +0300 From: Alexander Turenko Message-ID: <20201013004632.lh5sfqxcqxilerct@tkn_work_nb> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 2.X v3 2/3] module api: export box_key_def_dup List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Timur Safin Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org Everything is okay, but I would add a test case. You can use the box_key_def_dump_parts() function + the key_part_def_check_equal() helper to verify equality of two key_defs or create your own wrapper for two key_defs similar to key_def_check_merge() (see the recent branch re key_def APIs, I have updated it today). On Mon, Oct 12, 2020 at 03:44:10AM +0300, Timur Safin wrote: > Exporting `box_key_def_dup` as accessor to the internal `key_def_dup` > > Part of #5384