From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alyapunov@tarantool.org>
Received: from smtpng2.m.smailru.net (smtpng2.m.smailru.net [94.100.179.3])
 (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 46485445320
 for <tarantool-patches@dev.tarantool.org>;
 Wed,  8 Jul 2020 15:07:08 +0300 (MSK)
From: Aleksandr Lyapunov <alyapunov@tarantool.org>
Date: Wed,  8 Jul 2020 15:07:06 +0300
Message-Id: <1594210027-332-1-git-send-email-alyapunov@tarantool.org>
Subject: [Tarantool-patches] [PATCH] Fix make_scoped_guard usage
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: tarantool-patches@dev.tarantool.org

make_scoped_guard usually captures scope by [=].
In some cases it could lead to unexpected results.
I found several problems and fixed them.

GH issue: https://github.com/tarantool/tarantool/issues/5154
GH branch: https://github.com/tarantool/tarantool/tree/alyapunov/gh-5154-wrong-scoped-guards

Aleksandr Lyapunov (1):
  Fix wrong make_scoped_guard usage

 src/box/alter.cc | 4 ++--
 src/main.cc      | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.7.4