From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp54.i.mail.ru (smtp54.i.mail.ru [217.69.128.34]) (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 C5521469719 for ; Fri, 2 Oct 2020 19:12:25 +0300 (MSK) From: "Timur Safin" References: <20200929151946.GZ18920@tarantool.org> In-Reply-To: <20200929151946.GZ18920@tarantool.org> Date: Fri, 2 Oct 2020 19:12:25 +0300 Message-ID: <0acd01d698d6$d1a23460$74e69d20$@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Content-Language: ru Subject: Re: [Tarantool-patches] [PATCH 2.X 3/7] module api: luaT_newthread List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 'Igor Munkin' Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org, alexander.turenko@tarantool.org : From: Igor Munkin : Subject: Re: [Tarantool-patches] [PATCH 2.X 3/7] module api: : luaT_newthread : : Timur, : : Thanks for the patch, but I guess this one can be implemented using the : existing public interfaces (i.e. Lua C standart API + already exported : ). It was done to resolve the issue with Tarantool internal : crash[1] and I believe if user need to handle OOM error it can do it by : himself. : : [1]: https://github.com/tarantool/tarantool/issues/4556 : : -- : Best regards, : IM I do not quite get your point here - here we do want to use that newly introduced wrapper luaT_newthread in the external module. Do you suggest we reimplement it similarly in the external module? We tried and incr_top() was the problematic if we live outside of Tarantool core. Or do you mean that we do not want to deal with incr_top(L) from outside? Timur