Home | History | Annotate | Download | only in Sema

Lines Matching defs:Name

83     // If this nested-name-specifier refers to the current
98 // We are entering the context of the nested name specifier, so try to
99 // match the nested name specifier to either a primary class template
107 // If the type of the nested name specifier is the same as the
108 // injected class name of the named class template, we're entering
115 // If the type of the nested name specifier is the same as the
124 // The nested name specifier refers to a member of a class template.
134 llvm_unreachable("Dependent nested-name-specifier has no DeclContext");
145 assert(Tag && "Non-tag type in nested-name-specifier");
166 /// \brief If the given nested name specifier refers to the current
170 /// \param NNS a dependent nested name specifier.
173 assert(NNS->isDependent() && "Only dependent nested-name-specifier allowed");
185 /// complete enough (or can be made complete enough) for name lookup
285 /// result for name lookup of a nested-name-specifier.
286 /// \param SD Declaration checked for nested-name-specifier.
302 // a typedef thereof. If so, build the nested-name-specifier.
327 /// \brief If the given nested-name-specifier begins with a bare identifier
328 /// (e.g., Base::), perform name lookup for that identifier as a
329 /// nested-name-specifier within the given scope, and return the result of that
330 /// name lookup.
363 // Determine where to perform name lookup
367 // This nested-name-specifier occurs in a member access expression, e.g.,
373 // This nested-name-specifier occurs after another nested-name-specifier,
374 // so long into the context associated with the prior nested-name-specifier.
381 // Perform "qualified" name lookup into the declaration context we
384 // nested-name-specifier.
424 /// \brief Build a new nested-name-specifier for "identifier::", as described
427 /// \param S Scope in which the nested-name-specifier occurs.
431 /// \param ObjectType Type of postfix expression if the nested-name-specifier
434 /// nested-name-specifier.
435 /// \param SS Optional nested name specifier preceding the identifier.
436 /// \param ScopeLookupResult Provides the result of name lookup within the
437 /// scope of the nested-name-specifier that was computed at template
448 /// the result of name lookup within the scope of the nested-name-specifier
470 // Determine where to perform name lookup
476 // This nested-name-specifier occurs in a member access expression, e.g.,
482 // This nested-name-specifier occurs after another nested-name-specifier,
483 // so look into the context associated with the prior nested-name-specifier.
491 // Perform "qualified" name lookup into the declaration context we
494 // nested-name-specifier.
508 // class-name-or-namespace-name::...
510 // the class-name-or-namespace-name following the . or -> operator is
512 // the scope of the class of the object expression. If the name is found
513 // only in the scope of the class of the object expression, the name
514 // shall refer to a class-name. If the name is found only in the
515 // context of the entire postfix-expression, the name shall refer to a
516 // class-name or namespace-name. [...]
518 // Qualified name lookup into a class will not find a namespace-name,
520 // this qualified name lookup may find nothing. In that case, perform
521 // unqualified name lookup in the given scope (if available) or
522 // reconstruct the result from when name lookup was performed at template
532 // Perform unqualified name lookup in the current scope.
537 // that's fine: just build a dependent nested-name-specifier.
547 // base object type or prior nested-name-specifier, so this
548 // nested-name-specifier refers to an unknown specialization. Just build
549 // a dependent nested-name-specifier.
557 // If identifier is not found as class-name-or-namespace-name, but is found
588 DeclarationName Name = Found.getLookupName();
597 Name.getAsString() == Corrected.getAsString(getLangOpts());
601 << Name << LookupCtx << DroppedSpecifier
605 << Name);
626 // [...] If the name is found in both contexts, the
627 // class-name-or-namespace-name shall refer to the same entity.
629 // We already found the name in the scope of the object. Now, look
631 // see if we can find the same name there. As above, if there is no
660 // Fall through so that we'll pick the name we found in the object
669 // don't extend the nested-name-specifier. Just return now.
673 // The use of a nested name specifier may trigger deprecation warnings.
719 llvm_unreachable("Unhandled TypeDecl node in nested-name-specifier");
736 // ordinary name lookup, which can help us produce better error
747 // nested-name-specifier is located inside a dependent base class.
836 /// a nested name specifier, for example a namespace name. It is
875 // the template name.
913 // We were able to resolve the template name to an actual template.
914 // Build an appropriate nested-name-specifier.
921 // nested name specifiers.
946 /// \brief A structure that stores a nested-name-specifier annotation,
947 /// including both the nested-name-specifier
990 // In a friend declaration naming a member function, a name used
993 // function's class. If it is not found, or if the name is part of
1019 /// scope or nested-name-specifier) is parsed, part of a declarator-id.
1039 // Rebuild the nested name specifier for the new scope.