[NFC] fix trivial typos in comments
"a a"->"a" llvm-svn: 325753
This commit is contained in:
parent
7f9f92f8b6
commit
971514dd3e
|
@ -799,7 +799,7 @@ public:
|
|||
/// Potentially capturable variables of a nested lambda that might need
|
||||
/// to be captured by the lambda are housed here.
|
||||
/// This is specifically useful for generic lambdas or
|
||||
/// lambdas within a a potentially evaluated-if-used context.
|
||||
/// lambdas within a potentially evaluated-if-used context.
|
||||
/// If an enclosing variable is named in an expression of a lambda nested
|
||||
/// within a generic lambda, we don't always know know whether the variable
|
||||
/// will truly be odr-used (i.e. need to be captured) by that nested lambda,
|
||||
|
|
|
@ -23,7 +23,7 @@ namespace {
|
|||
// clang-cl implements the following simpler (but largely compatible) behavior
|
||||
// instead:
|
||||
// * [] and __declspec uuids have the same behavior.
|
||||
// * If there are several uuids on a a class (no matter if on the same decl or
|
||||
// * If there are several uuids on a class (no matter if on the same decl or
|
||||
// on several decls), it is an error if they don't match.
|
||||
// * Having several uuids that match is ok.
|
||||
|
||||
|
|
Loading…
Reference in New Issue