Lines Matching refs:braces

495 formatting braced initialization lists: act as-if the braces were parentheses
643   // The Foo constructor call is reading a file, don't use braces to call it.
646   // The pair is being constructed like an aggregate, use braces.
1270 braces, and keeps the conceptual context cleaner.  The general form of this rule
1588 prefer to omit the braces to avoid unnecessary line noise. However, braces
1589 should be used in cases where the omission of braces harm the readability and
1596 Similarly, braces should be used when a single-statement body is complex enough
1613   // Omit the braces since the body is simple and clearly associated with the
1623     // comment, so it would be unclear without the braces whether the following
1630   // Use braces on the outer `if` to avoid a potential dangling `else`
1637   // Use braces for the `if` block to keep it uniform with the `else` block.
1642     // this surprisingly long comment, so it would be unclear without the braces
1647   // This should also omit braces.  The `for` loop contains only a single
1648   // statement, so it shouldn't have braces.  The `if` also only contains a
1649   // single simple statement (the `for` loop), so it also should omit braces.
1654   // Use braces for a `do-while` loop and its enclosing statement.
1661   // Use braces for the outer `if` since the nested `for` is braced.
1665       // with this surprisingly long comment, forcing braces on the `for` block.
1670   // Use braces on the outer block because there are more than two levels of
1678   // Use braces on the outer block because of a nested `if`; otherwise the
1679   // compiler would warn: `add explicit braces to avoid dangling else`