From b649f288acddf6105b5dae28ea6d69b82176cf8b Mon Sep 17 00:00:00 2001
From: Christian Kandeler <christian.kandeler@qt.io>
Date: Tue, 12 Apr 2022 12:59:40 +0200
Subject: [PATCH] ClangCodeModel: Another output argument highlighting fix

Change-Id: I2b784c32706a4eaa837cf999884656d62b253e3d
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: David Schulz <david.schulz@qt.io>
---
 src/plugins/clangcodemodel/clangdclient.cpp | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/plugins/clangcodemodel/clangdclient.cpp b/src/plugins/clangcodemodel/clangdclient.cpp
index 16c20647eb9..f30c18aa7f6 100644
--- a/src/plugins/clangcodemodel/clangdclient.cpp
+++ b/src/plugins/clangcodemodel/clangdclient.cpp
@@ -2714,6 +2714,8 @@ static void semanticHighlighter(QFutureInterface<HighlightingResult> &future,
                 // the call happens, and should not be highlighted as an output argument.
                 // If the call is not fully resolved (as in templates), we don't
                 // know whether the argument is passed as const or not.
+                if (it->arcanaContains("dependent type"))
+                    return false;
                 const QList<AstNode> children = it->children().value_or(QList<AstNode>());
                 return children.isEmpty()
                         || (children.first().range() != (it - 1)->range()