From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng1.m.smailru.net (smtpng1.m.smailru.net [94.100.181.251]) (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 A165A44643E for ; Thu, 15 Oct 2020 02:41:54 +0300 (MSK) References: <6753bd0b7bc224dfb7634b2242075d4a164ff949.1602541394.git.alexander.turenko@tarantool.org> From: Vladislav Shpilevoy Message-ID: Date: Thu, 15 Oct 2020 01:41:53 +0200 MIME-Version: 1.0 In-Reply-To: <6753bd0b7bc224dfb7634b2242075d4a164ff949.1602541394.git.alexander.turenko@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH v3 08/16] module api/lua: add API_EXPORT to tuple functions List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko Cc: tarantool-patches@dev.tarantool.org Thanks for the patch! On 13.10.2020 01:23, Alexander Turenko wrote: > The reason is unification of declarations. It is the rule of thumb to > use API_EXPORT with module API functions. What about box_tuple_ref, box_tuple_unref, box_tuple_field_count, and other tuple functions?