Lines Matching full:specifier

61     // If this nested-name-specifier refers to the current
76         // We are entering the context of the nested name specifier, so try to
77         // match the nested name specifier to either a primary class template
113                                          "specifier in SFINAE context?");
122           // If the type of the nested name specifier is the same as the
131         // The nested name specifier refers to a member of a class template.
141     llvm_unreachable("Dependent nested-name-specifier has no DeclContext");
152     assert(Tag && "Non-tag type in nested-name-specifier");
175   assert(NNS->isDependent() && "Only dependent nested-name-specifier allowed");
334   // a typedef thereof. If so, build the nested-name-specifier.
427     // This nested-name-specifier occurs in a member access expression, e.g.,
429     assert(!SS.isSet() && "ObjectType and scope specifier cannot coexist");
433     // This nested-name-specifier occurs after another nested-name-specifier,
434     // so look into the context associated with the prior nested-name-specifier.
445     // nested-name-specifier.
491   // that's fine: just build a dependent nested-name-specifier.
501     // base object type or prior nested-name-specifier, so this
502     // nested-name-specifier refers to an unknown specialization. Just build
503     // a dependent nested-name-specifier.
631     // don't extend the nested-name-specifier. Just return now.
635     // The use of a nested name specifier may trigger deprecation warnings.
688       llvm_unreachable("Unhandled TypeDecl node in nested-name-specifier");
713   // nested-name-specifier is located inside a dependent base class.
734         // Fake up a nested-name-specifier that starts with the
912   // Build an appropriate nested-name-specifier.
943   /// A structure that stores a nested-name-specifier annotation,
944   /// including both the nested-name-specifier
1035   // Rebuild the nested name specifier for the new scope.