From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alexander.turenko@tarantool.org>
Received: from smtp44.i.mail.ru (smtp44.i.mail.ru [94.100.177.104])
 (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 65B00452566
 for <tarantool-patches@dev.tarantool.org>;
 Wed, 13 Nov 2019 11:40:20 +0300 (MSK)
Date: Wed, 13 Nov 2019 11:40:17 +0300
From: Alexander Turenko <alexander.turenko@tarantool.org>
Message-ID: <20191113084016.re4q3xhca3gj56c2@tkn_work_nb>
References: <c5ad5ef9e4aecd36d9feb3bb076ceae401d3e1db.1573259560.git.alexander.turenko@tarantool.org>
 <686ed898-91d1-546e-6120-ed7b1f46e1d7@tarantool.org>
 <20191112174047.tirafxzpyiytkxfl@tkn_work_nb>
 <03c537b9-b903-6cec-4f52-e313f3486754@tarantool.org>
 <20191112210318.mv7pfsg3dvyhpxng@tkn_work_nb>
 <7d91f7dc-99ac-5c05-8ac1-e256f8dde393@tarantool.org>
 <20191113043358.GA1534@atlas>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20191113043358.GA1534@atlas>
Subject: Re: [Tarantool-patches] [PATCH] app/argparse: expect no value for a
 boolean option
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Konstantin Osipov <kostja.osipov@gmail.com>
Cc: tarantool-patches@dev.tarantool.org, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>

On Wed, Nov 13, 2019 at 07:33:59AM +0300, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/11/13 07:15]:
> > >>> As I see the first and the second variants are used across tarantool's
> > >>> built-in Lua code. You are right, third one, which I personally prefer,
> > >>> is not used within the project.
> > >>
> > >> There is no options. The first is the only standard in our code. If the
> > >> second one is used somewhere, then it is incorrect, or is a third-party
> > >> library with own code style.
> > > 
> > > I see no mentions about this (at least there is nothing about this in
> > > our Lua Style Guide on the website) as well as I see no dominant style
> > > across our Lua code.
> > > 
> > > What is the source of your information?
> > > 
> > 
> > I remember, that I tried once to use a not aligned multiline 'if' and
> > was said/emailed by you, or Roman T., or Vladimir D., or by Kostja O.,
> > that in Lua we need to stick to the same rules as in C about alignment.
> 
> there is lua coding style that was added by Eugene. I believe it
> is even online in the docs:
> 
> https://www.tarantool.io/en/doc/1.10/dev_guide/lua_style_guide/
> 
> The code should stick to it.

It does not contain anything about a line continuation. One of three
linked style guides does, but it is a double indent.