Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>,
	tarantool-patches@dev.tarantool.org, lvasiliev@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/3] luacheck: fix warnings in test/box
Date: Thu, 14 Jan 2021 10:49:51 +0300	[thread overview]
Message-ID: <2157981c-bfb3-3c4c-0090-fdd0931f88fa@tarantool.org> (raw)
In-Reply-To: <ef5511e5-59a4-e3ef-b3d3-fb32711a346f@tarantool.org>


On 13.01.2021 19:38, Vladislav Shpilevoy wrote:
> Hi! Thanks for the fixes!
>
> Consider my fixes on top of this commit on the branch, and below with
> explanations.
Thanks for your fixes! I have squashed your commit.

<snipped>

> @@ -50,11 +50,11 @@ local function test_insert_delete(n)
>   end
>   
>   return {
> -    clear = clear;
> -    create_space = create_space;
> -    delete = delete;
> -    drop_space = drop_space;
> -    dump = dump;
> -    fill = fill;
> -    test_insert_delete = test_insert_delete;
> +    clear = clear,
> +    create_space = create_space,
> +    delete = delete,
> +    drop_space = drop_space,
> +    dump = dump,
> +    fill = fill,
> +    test_insert_delete = test_insert_delete,
> ====================
>
> We don't use ';' anywhere. It may still be used in some old code,
> but not in the new code. I have no idea though if it is stated
> anywhere formally.

actually there is a rule in Lua guideline [1]: "do not use semicolon as 
table separator (only comma)"

<snipped>

1. 
https://www.tarantool.io/en/doc/latest/dev_guide/lua_style_guide/#idioms-and-patterns



  reply	other threads:[~2021-01-14  7:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 14:54 [Tarantool-patches] [PATCH v7 0/3] Fix luacheck warnings in test/box-tap, test/box and test/box-py sergeyb
2020-12-22 14:54 ` [Tarantool-patches] [PATCH 1/3] luacheck: fix warnings in test/box sergeyb
2021-01-11 17:52   ` Vladislav Shpilevoy via Tarantool-patches
2021-01-12 15:26     ` Sergey Bronnikov via Tarantool-patches
2021-01-13  7:58       ` Sergey Bronnikov via Tarantool-patches
2021-01-13 16:38       ` Vladislav Shpilevoy via Tarantool-patches
2021-01-14  7:49         ` Sergey Bronnikov via Tarantool-patches [this message]
2020-12-22 14:54 ` [Tarantool-patches] [PATCH v7 2/3] luacheck: fix warnings in test/box-py sergeyb
2020-12-22 14:54 ` [Tarantool-patches] [PATCH v7 3/3] luacheck: fix warnings in test/box-tap sergeyb
2021-01-11 17:52   ` Vladislav Shpilevoy via Tarantool-patches
2021-01-12 13:59     ` Sergey Bronnikov via Tarantool-patches
2021-01-12 14:52       ` Vladislav Shpilevoy via Tarantool-patches
2021-01-12 15:21         ` Sergey Bronnikov via Tarantool-patches
2020-12-25 10:37 ` [Tarantool-patches] [PATCH v7 0/3] Fix luacheck warnings in test/box-tap, test/box and test/box-py Kirill Yukhin
2020-12-30 10:17   ` Kirill Yukhin
2020-12-30 12:27 ` Leonid Vasiliev
2021-01-14 21:34 ` Vladislav Shpilevoy via Tarantool-patches
2021-01-15  9:48 ` Kirill Yukhin via Tarantool-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2157981c-bfb3-3c4c-0090-fdd0931f88fa@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=lvasiliev@tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 1/3] luacheck: fix warnings in test/box' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox