Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov <sergeyb@tarantool.org>
To: Oleg Babin <olegrok@tarantool.org>, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] Fix luacheck warnings in src/lua/*.lua
Date: Tue, 7 Apr 2020 18:39:13 +0300	[thread overview]
Message-ID: <20200407153913.GC5989@pony.bronevichok.ru> (raw)
In-Reply-To: <20200406093343.GB20529@pony.bronevichok.ru>

Oleg,

On 12:33 Mon 06 Apr , Sergey Bronnikov wrote:
> > On 03/04/2020 12:39, Sergey Bronnikov wrote:
> > > diff --git a/src/lua/tap.lua b/src/lua/tap.lua
> > > index 94b080d5a..04497386e 100644
> > > --- a/src/lua/tap.lua
> > > +++ b/src/lua/tap.lua
> > > @@ -53,7 +53,7 @@ local function ok(test, cond, message, extra)
> > >       io.write(string.format("not ok - %s\n", message))
> > >       extra = extra or {}
> > >       if test.trace then
> > > -        local frame = debug.getinfo(3, "Sl")
> > > +        debug.getinfo(3, "Sl")
> > 
> > I think debug.getinfo() could be completely removed. It doesn't change any
> > state it only returns some debug information that is completely unused.
> 
> This patch is about fixing warnings produced by luacheck,
> Proposed change doesn't relate to Lua static analysis, so I suggest
> to make it in a separate patch.

I was wrong, 'frame' is unused here and can be removed, Vlad Sh. also
reminded me about it.

  reply	other threads:[~2020-04-07 15:39 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 [this message]
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
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=20200407153913.GC5989@pony.bronevichok.ru \
    --to=sergeyb@tarantool.org \
    --cc=olegrok@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