From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [87.239.111.99] (localhost [127.0.0.1]) by dev.tarantool.org (Postfix) with ESMTP id F0B888205E; Sun, 24 Jan 2021 19:26:32 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org F0B888205E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1611505593; bh=o5y/RSbMo3GGArfALPBcHfbqYWgfjxMEvzMtmQitfsk=; h=To:References:Date:In-Reply-To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=agnDRkqR+WdojxFaWGzI/sPLhxcFUCpSeEd/g/p4/Brab/9GLo15Rb2C0NejqziEO mOYiaSbyRCjrirQZL05fZB9C/RKkZPl5QNkgK96D6CTfGob2VMnf7nWY1c4yZgj/76 LkuA/r9+ATThJc+lw0Q/jr4jPcbuniJV8jWxjBjU= Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (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 356888205E for ; Sun, 24 Jan 2021 19:26:29 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 356888205E Received: by smtpng3.m.smailru.net with esmtpa (envelope-from ) id 1l3iDc-0002Dl-Hx; Sun, 24 Jan 2021 19:26:28 +0300 To: Cyrill Gorcunov , tml References: <20210118203556.281700-1-gorcunov@gmail.com> Message-ID: Date: Sun, 24 Jan 2021 17:26:27 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <20210118203556.281700-1-gorcunov@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-7564579A: B8F34718100C35BD X-77F55803: 4F1203BC0FB41BD9F0E84CC1954AA43820AFEE167473C3281A531C928E5BB44000894C459B0CD1B9D6A215C7E4B7949BBED5166B351F634FE677AB1C9F20D3C86C140D91676DDD80 X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE782A779A89F7D69B2C2099A533E45F2D0395957E7521B51C2CFCAF695D4D8E9FCEA1F7E6F0F101C6778DA827A17800CE70A10A23A3B64B805EA1F7E6F0F101C674E70A05D1297E1BBC6CDE5D1141D2B1C0B1F46A4AF37D13B464F27A3C9D9984F10F38D3CA2525E739FA2833FD35BB23D9E625A9149C048EE33AC447995A7AD182CC0D3CB04F14752D2E47CDBA5A96583BD4B6F7A4D31EC0BC014FD901B82EE079FA2833FD35BB23D27C277FBC8AE2E8BAA867293B0326636D2E47CDBA5A96583BA9C0B312567BB23089D37D7C0E48F6CA18204E546F3947C890A246B268E114E57739F23D657EF2BC8A9BA7A39EFB7666BA297DBC24807EA089D37D7C0E48F6C8AA50765F79006378534F7D0DA3B5694EFF80C71ABB335746BA297DBC24807EA27F269C8F02392CD4DF8A859A081327B27F269C8F02392CD5571747095F342E88FB05168BE4CE3AF X-C1DE0DAB: 0D63561A33F958A57490513314FA1F10B76E5997A48AC99C5AC8269A409946BAD59269BC5F550898D99A6476B3ADF6B47008B74DF8BB9EF7333BD3B22AA88B938A852937E12ACA758F9E841AEAEC4F2C410CA545F18667F91A7EA1CDA0B5A7A0 X-C8649E89: 4E36BF7865823D7055A7F0CF078B5EC49A30900B95165D34A533D6DF7731C6647F2BCB084C50BBB9D66FAEF1A4F1A54CE577A461E816FB1CD6F5A51C696837C91D7E09C32AA3244C9EF197F95D6B3BABA028641577EE1139F26BFA4C8A6946B8729B2BEF169E0186 X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu530nj6fImhcD4MUrOEAnl0W826KZ9Q+tr5ycPtXkTV4k65bRjmOUUP8cvGozZ33TWg5HZplvhhXbhDGzqmQDTd6OAevLeAnq3Ra9uf7zvY2zzsIhlcp/Y7m53TZgf2aB4JOg4gkr2biojEcKN7r9rK/31lItVb/pOag== X-Mailru-Sender: 689FA8AB762F73936BC43F508A0638229965FBEFC3A1A97023EFD1D831B8D98C3841015FED1DE5223CC9A89AB576DD93FB559BB5D741EB963CF37A108A312F5C27E8A8C3839CE0E267EA787935ED9F1B X-Mras: Ok Subject: Re: [Tarantool-patches] [PATCH v12 0/8] box: implement cmod Lua module X-BeenThere: tarantool-patches@dev.tarantool.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Vladislav Shpilevoy via Tarantool-patches Reply-To: Vladislav Shpilevoy Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" Hi! Thanks for the patchset! > v12: > - switch to new API as been discussed in > https://lists.tarantool.org/tarantool-patches/e186c454-6765-4776-6433-f3f791ff4c27@tarantool.org/ This is what I meant when I asked for a proper API design which we could strictly follow. The thing by the link is not a discussion. It is some questions from me + your response talking about implementation and other assumptions/proposals. I still don't see an approved API design on which all the interested people would agree. I simply don't know how to review the user-visible part of this patch because I don't know how it should work. There is no design, the API in the patch just happened to be this.