From 86bd6eaa752bda945779b80ecdc30e984dff2a81 Mon Sep 17 00:00:00 2001 From: Max Brunsfeld Date: Mon, 16 Mar 2015 22:00:02 -0700 Subject: [PATCH] Use make_tuple, not initializer list syntax gcc requires it. clang doesn't. --- src/compiler/build_tables/parse_conflict_manager.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compiler/build_tables/parse_conflict_manager.cc b/src/compiler/build_tables/parse_conflict_manager.cc index 21ebaa13..7532d148 100644 --- a/src/compiler/build_tables/parse_conflict_manager.cc +++ b/src/compiler/build_tables/parse_conflict_manager.cc @@ -25,7 +25,7 @@ ParseConflictManager::resolve(const ParseAction &new_action, const rules::Symbol &symbol) const { if (new_action.type < old_action.type) { auto opposite = resolve(old_action, new_action, symbol); - return { !get<0>(opposite), get<1>(opposite), get<2>(opposite) }; + return make_tuple(!get<0>(opposite), get<1>(opposite), get<2>(opposite)); } switch (old_action.type) {