Lines Matching full:dependent

49   //   dependent member of the current instantiation is value-dependent. An
50 // expression of the form & cast-expression is also value-dependent if
78 // Never type-dependent (C++ [temp.dep.expr]p3).
79 // Value-dependent if the argument is type-dependent.
86 // Value-dependent if the argument is type-dependent.
90 // dependent because decl's alignment is dependent.
143 // Cast expressions are type-dependent if the type is
144 // dependent (C++ [temp.dep.expr]p3).
145 // Cast expressions are value-dependent if the type is
146 // dependent or if the subexpression is value-dependent.
150 // dependent, but it may be deduced as a dependent type.
167 // [temp.dep.expr] does specify state that this should be dependent on ALL sub
184 // Note: we treat a statement-expression in a dependent context as always
185 // being value- and instantiation-dependent. This matches the behavior of
289 // typeid is never type-dependent (C++ [temp.dep.expr]p4)
310 // 'this' is type-dependent if the class type of the enclosing
311 // member function is dependent (C++ [temp.dep.expr]p2)
316 // is type-dependent, so is the object and thus 'this'.
319 // to do this so we can mark NSDM accesses as dependent.
357 // Never type-dependent.
359 // Value-dependent if the argument is type-dependent.
479 // If the type is omitted, it's 'int', and is not dependent in any way.
503 ~NestedNameSpecifierDependence::Dependent);
520 // An id-expression is type-dependent if it contains:
523 // declared with a dependent type
527 // type is dependent ([dcl.fct]),
531 // dependent type if they involve a placeholder type that can't be deduced.]
542 // - a conversion-function-id that specifies a dependent type
553 // - a template-id that is dependent,
558 // or if it names a dependent member of the current instantiation that is a
563 // An id-expression is value-dependent if:
565 // - it is type-dependent [handled above]
572 // expression that is value-dependent
583 // - it names a static data member that is a dependent member of the
600 // - it names a static member function that is a dependent member of the
606 // which makes the overall expression value-dependent.
617 // - always value-dependent, and therefore instantiation dependent
619 // - type-dependent if we don't know the type (fallback to an opaque
620 // dependent type), or the type is known and dependent, or it has
621 // type-dependent subexpressions.
624 // FIXME: remove the type-dependent bit from subexpressions, if the
625 // RecoveryExpr has a non-dependent type.
677 ~NestedNameSpecifierDependence::Dependent);
693 // Bitfield with value-dependent width is type-dependent.
787 ~NestedNameSpecifierDependence::Dependent);
805 ~NestedNameSpecifierDependence::Dependent);
811 // If we have explicit template arguments, check for dependent