From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v2] Fix warnings
Date: Fri, 21 Sep 2018 15:35:29 +0300 [thread overview]
Message-ID: <20180921123529.brpmozsogtdv53p2@tkn_work_nb> (raw)
In-Reply-To: <20180426063849.7mmx4ch3esv3x2cc@tarantool.org>
I think we should use MAYBE_UNUSED for a function parameter and (void)
for a function variable. At least it seems we now use them it that way.
WBR, Alexander Turenko.
On Thu, Apr 26, 2018 at 09:38:49AM +0300, Kirill Yukhin wrote:
> Hello Gleb,
> On 23 апр 20:08, Gleb wrote:
> > Ensure -Werror -Wall set for the whole src/.
> > Fix warnings which have been found with -Werror and -Wall.
> > Add new build target RelWithDebInfoWError.
> > Change build target on RelWithDebInfoWError in CI.
> >
> > Fixes #3238
> > ---
> > diff --git a/src/box/space_def.c b/src/box/space_def.c
> > index 22bd3ca..3f11088 100644
> > --- a/src/box/space_def.c
> > +++ b/src/box/space_def.c
> > @@ -130,6 +130,7 @@ space_def_dup(const struct space_def *src)
> > * allocation refactoring.
> > */
> > assert(expr_pos_old == expr_pos);
> > + (void) expr_pos_old;
> Could you pls use MAYBE_UNUSED, defined in util/trivia.h, instead?
> (everywhere in your patch)
>
> --
> Regards, Kirill Yukhin
>
next prev parent reply other threads:[~2018-09-21 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 17:08 [tarantool-patches] " Gleb
2018-04-23 17:37 ` [tarantool-patches] " n.pettik
2018-04-26 6:38 ` Kirill Yukhin
2018-09-21 12:35 ` Alexander Turenko [this message]
2018-09-21 16:41 ` [tarantool-patches] [PATCH] Add -Werror for CI (1.10 part) Alexander Turenko
2018-09-21 16:41 ` [tarantool-patches] [PATCH] Fix RelWithDebInfoWError warnings on 2.0 Alexander Turenko
2018-10-05 6:06 ` [tarantool-patches] " Alexander Turenko
2018-10-05 7:42 ` Kirill Yukhin
2018-10-05 7:20 ` [tarantool-patches] Re: [PATCH] Add -Werror for CI (1.10 part) Kirill Yukhin
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 13:50 [tarantool-patches] [PATCH v2] Fix warnings Gleb
2018-04-18 12:13 ` [tarantool-patches] " Alexander Turenko
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=20180921123529.brpmozsogtdv53p2@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2] Fix warnings' \
/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