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