From 0718c6fae002a37b7448bf4b5841d08de114050e Mon Sep 17 00:00:00 2001
From: Jacques Lucke <jacques@blender.org>
Date: Mon, 13 Jul 2020 10:40:05 +0200
Subject: [PATCH] Cleanup: fix clang tidy warning

The code was actually correct, but clang tidy complaint about
using the Vector after it was moved from.
---
 .../functions/intern/multi_function_network_optimization.cc    | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/source/blender/functions/intern/multi_function_network_optimization.cc b/source/blender/functions/intern/multi_function_network_optimization.cc
index 4fe0b506df8..849b24a318f 100644
--- a/source/blender/functions/intern/multi_function_network_optimization.cc
+++ b/source/blender/functions/intern/multi_function_network_optimization.cc
@@ -454,8 +454,9 @@ static void relink_duplicate_nodes(MFNetwork &network,
     }
 
     Vector<MFNode *, 16> nodes_to_check = nodes_with_same_hash;
-    Vector<MFNode *, 16> remaining_nodes;
     while (nodes_to_check.size() >= 2) {
+      Vector<MFNode *, 16> remaining_nodes;
+
       MFNode &deduplicated_node = *nodes_to_check[0];
       for (MFNode *node : nodes_to_check.as_span().drop_front(1)) {
         /* This is true with fairly high probability, but hash collisions can happen. So we have to