From: Igor Munkin <imun@tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: o.piskunov@tarantool.org, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] Fix luacheck warnings in src/lua/*.lua
Date: Sat, 4 Apr 2020 12:34:57 +0300 [thread overview]
Message-ID: <20200404093457.GC30022@tarantool.org> (raw)
In-Reply-To: <20200403093902.GA42848@pony.bronevichok.ru>
Sergey,
Thanks for the patch. It's not a review, I just want to add my two cents
regarding luacheck usage.
1. Please consider the way style violations are organized in uJIT
repo[1]. You can also group everything into a single file for better
further maintenance.
2. There is also a runner[2] for luacheck, that considers uJIT specifics
(e.g. ujit table is a global variable similar to Tarantool's box one).
I guess this approach should be considered, even if you decide to make
the patch your own way.
On 03.04.20, Sergey Bronnikov wrote:
> GitHub branch: https://github.com/tarantool/tarantool/tree/ligurio/gh-4681-fix-luacheck-warnings
>
> How-to check:
>
> $ tarantoolctl rocks install luacheck
> $ .rocks/bin/luacheck src/lua/*.lua
>
> ---
> src/lua/argparse.lua | 6 ++--
> src/lua/buffer.lua | 4 +--
> src/lua/clock.lua | 2 +-
> src/lua/crypto.lua | 18 +++++-----
> src/lua/csv.lua | 5 ++-
> src/lua/digest.lua | 6 ++--
> src/lua/env.lua | 2 +-
> src/lua/errno.lua | 2 +-
> src/lua/fio.lua | 28 ++++++++--------
> src/lua/help.lua | 24 +++++++-------
> src/lua/httpc.lua | 3 --
> src/lua/init.lua | 17 +++++-----
> src/lua/msgpackffi.lua | 15 ++++-----
> src/lua/socket.lua | 66 ++++++++++++++++++-------------------
> src/lua/string.lua | 1 -
> src/lua/swim.lua | 20 +++++------
> src/lua/tap.lua | 75 ++++++++++++++++++++----------------------
> src/lua/trigger.lua | 3 --
> 18 files changed, 142 insertions(+), 155 deletions(-)
>
<snipped>
>
> --
> sergeyb@
[1]: https://github.com/iponweb/luavela/blob/master/.luacheckrc
[2]: https://github.com/iponweb/luavela/blob/master/scripts/run-luacheck
--
Best regards,
IM
next prev parent reply other threads:[~2020-04-04 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 9:39 Sergey Bronnikov
2020-04-03 10:13 ` lvasiliev
2020-04-03 11:03 ` Sergey Bronnikov
2020-04-03 14:21 ` Oleg Babin
2020-04-06 9:33 ` Sergey Bronnikov
2020-04-07 15:39 ` Sergey Bronnikov
2020-04-03 20:39 ` Vladislav Shpilevoy
2020-04-03 22:39 ` Vladislav Shpilevoy
2020-04-07 15:35 ` Sergey Bronnikov
2020-04-04 9:34 ` Igor Munkin [this message]
2020-04-07 15:15 ` Sergey Bronnikov
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=20200404093457.GC30022@tarantool.org \
--to=imun@tarantool.org \
--cc=o.piskunov@tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] Fix luacheck warnings in src/lua/*.lua' \
/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