forked from OSchip/llvm-project
Allow breaking after "::" if absolutely necessary.
Otherwise, really long nested name specifiers can easily lead to a violation of the column limit. Not sure about the rules for indentation in those cases, so input is appreciated (see tests.). llvm-svn: 173438
This commit is contained in:
parent
3eb45a03af
commit
45797021b7
|
@ -688,6 +688,8 @@ private:
|
|||
return 50;
|
||||
if (Left.is(tok::equal) && Right.is(tok::l_brace))
|
||||
return 150;
|
||||
if (Left.is(tok::coloncolon))
|
||||
return 500;
|
||||
|
||||
// In for-loops, prefer breaking at ',' and ';'.
|
||||
if (RootToken.is(tok::kw_for) &&
|
||||
|
@ -1597,10 +1599,11 @@ private:
|
|||
return (isBinaryOperator(Left) && Left.isNot(tok::lessless)) ||
|
||||
Left.is(tok::comma) || Right.is(tok::lessless) ||
|
||||
Right.is(tok::arrow) || Right.is(tok::period) ||
|
||||
Right.is(tok::colon) || Left.is(tok::semi) ||
|
||||
Left.is(tok::l_brace) || Left.is(tok::question) || Left.Type ==
|
||||
TT_ConditionalExpr || (Left.is(tok::r_paren) && Left.Type !=
|
||||
TT_CastRParen && Right.is(tok::identifier)) ||
|
||||
Right.is(tok::colon) || Left.is(tok::coloncolon) ||
|
||||
Left.is(tok::semi) || Left.is(tok::l_brace) ||
|
||||
Left.is(tok::question) || Left.Type == TT_ConditionalExpr ||
|
||||
(Left.is(tok::r_paren) && Left.Type != TT_CastRParen &&
|
||||
Right.is(tok::identifier)) ||
|
||||
(Left.is(tok::l_paren) && !Right.is(tok::r_paren));
|
||||
}
|
||||
|
||||
|
|
|
@ -1204,6 +1204,33 @@ TEST_F(FormatTest, WrapsTemplateDeclarations) {
|
|||
"void f();");
|
||||
}
|
||||
|
||||
TEST_F(FormatTest, WrapsAtNestedNameSpecifiers) {
|
||||
verifyFormat(
|
||||
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::\n"
|
||||
" aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa();");
|
||||
verifyFormat(
|
||||
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::\n"
|
||||
" aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa(\n"
|
||||
" aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa());");
|
||||
|
||||
// FIXME: Should we have an extra indent after the second break?
|
||||
verifyFormat(
|
||||
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::\n"
|
||||
" aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::\n"
|
||||
" aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa();");
|
||||
|
||||
// FIXME: Look into whether we should indent 4 from the start or 4 from
|
||||
// "bbbbb..." here instead of what we are doing now.
|
||||
verifyFormat(
|
||||
"aaaaaaaaaaaaaaa(bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb::\n"
|
||||
" cccccccccccccccccccccccccccccccccccccccccccccccccc());");
|
||||
|
||||
// Breaking at nested name specifiers is generally not desirable.
|
||||
verifyFormat(
|
||||
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa(\n"
|
||||
" aaaaaaaaaaaaaaaaaaaaaaa);");
|
||||
}
|
||||
|
||||
TEST_F(FormatTest, UnderstandsTemplateParameters) {
|
||||
verifyFormat("A<int> a;");
|
||||
verifyFormat("A<A<A<int> > > a;");
|
||||
|
|
Loading…
Reference in New Issue