From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f66.google.com (mail-lf1-f66.google.com [209.85.167.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id A2F2B45C316 for ; Tue, 14 Apr 2020 15:29:48 +0300 (MSK) Received: by mail-lf1-f66.google.com with SMTP id 131so9181010lfh.11 for ; Tue, 14 Apr 2020 05:29:48 -0700 (PDT) Date: Tue, 14 Apr 2020 15:29:45 +0300 From: Cyrill Gorcunov Message-ID: <20200414122945.GF3072@uranus> References: <9c95d9dbd375121060090b71e8243a57c4f3ee89.1586862436.git.alexander.turenko@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9c95d9dbd375121060090b71e8243a57c4f3ee89.1586862436.git.alexander.turenko@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 09/12] popen: clarify popen_{signal, delete} contract List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko Cc: tarantool-patches@dev.tarantool.org On Tue, Apr 14, 2020 at 02:38:18PM +0300, Alexander Turenko wrote: > It is convenient to have a formal description of an API during > development and when writing a documentation. I plan to use those > contracts when I will write an API description for the future popen Lua > module. > > Part of #4031 Acked-by: Cyrill Gorcunov