Commit 7be3e8b5 authored by Milian Wolff's avatar Milian Wolff

Expect new failure in completion of switch labels

Seems like clang lost its smartness when completing switch labels.
It suggest non-constant expressions suddenly, which isn't even
valid C++. We need to fix that upstream somehow.
parent 275d8778
......@@ -30,6 +30,7 @@
#include <tests/testproject.h>
#include "duchain/parsesession.h"
#include "duchain/clanghelpers.h"
#include "util/clangtypes.h"
#include <interfaces/idocumentcontroller.h>
......@@ -49,6 +50,8 @@
#include <KConfigGroup>
#include <QVersionNumber>
QTEST_MAIN(TestCodeCompletion)
static const auto NoMacroOrBuiltin = ClangCodeCompletionContext::ContextFilters(
......@@ -179,6 +182,10 @@ void executeCompletionTest(const ReferencedTopDUContext& top, const CompletionIt
}
if (QTest::currentTestFunction() == QByteArrayLiteral("testClangCodeCompletion")) {
QEXPECT_FAIL("look-ahead pointer", "self-assignment isn't done anymore, so we don't find any suitable type anymore", Continue);
if (QVersionNumber::fromString(ClangHelpers::clangVersion()) >= QVersionNumber(9, 0, 0)) {
QEXPECT_FAIL("enum-case", "quite a lot of unrelated cruft is suggested, needs to be fixed upstream", Continue);
}
}
if (tester.names.size() != expectedCompletionItems.completions.size()) {
qDebug() << "different results:\nactual:" << tester.names << "\nexpected:" << expectedCompletionItems.completions;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment