Skip to content
  1. Mar 12, 2012
    • Richard Smith's avatar
      Fix parsing of type-specifier-seq's. Types are syntactically allowed to be · c5b05520
      Richard Smith authored
      defined here, but not semantically, so
      
        new struct S {};
      
      is always ill-formed, even if there is a struct S in scope.
      
      We also had a couple of bugs in ParseOptionalTypeSpecifier caused by it being
      under-loved (due to it only being used in a few places) so merge it into
      ParseDeclarationSpecifiers with a new DeclSpecContext. To avoid regressing, this
      required improving ParseDeclarationSpecifiers' diagnostics in some cases. This
      also required teaching ParseSpecifierQualifierList about constexpr... which
      incidentally fixes an issue where we'd allow the constexpr specifier in other
      bad places.
      
      llvm-svn: 152549
      c5b05520
    • Nick Lewycky's avatar
      Fix typo in comment, 'langauge' -> 'language'. · 74655a5d
      Nick Lewycky authored
      llvm-svn: 152547
      74655a5d
  2. Mar 11, 2012
  3. Mar 10, 2012
Loading