From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp46.i.mail.ru (smtp46.i.mail.ru [94.100.177.106]) (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 83AC2469719 for ; Mon, 12 Oct 2020 09:11:16 +0300 (MSK) Date: Mon, 12 Oct 2020 09:11:35 +0300 From: Alexander Turenko Message-ID: <20201012061135.6mxkxphxvvxuwsjv@tkn_work_nb> References: <9b2939cb-d2fe-e22d-41e4-0c653f04ddf7@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <9b2939cb-d2fe-e22d-41e4-0c653f04ddf7@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v2 07/15] module api/lua: expose luaT_tuple_new() List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org > > + * The new tuple is referenced in the same way as one created by > > + * (). There are two possible usage scenarious: > > + * > > + * 1. A short living tuple may not be referenced explicitly and > > + * will be collected automatically at the next module API call > > + * that yields or returns a tuple. > > + * 2. A long living tuple must be referenced using > > + * () and unreferenced than with > > than -> then. Thanks!