Tracking exception specification source locations
Summary: We do not currently track the source locations for exception specifications such that their source range can be queried through the AST. This leads to trying to write more complex code to determine the source range for uses like FixItHints (see D18575 for an example). In addition to use within tools like clang-tidy, I think this information may become more important to track as exception specifications become more integrated into the type system. Patch by Don Hinton. Reviewers: rsmith Subscribers: malcolm.parsons, sbarzowski, alexfh, hintonda, cfe-commits Differential Revision: https://reviews.llvm.org/D20428 git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@291771 91177308-0d34-0410-b5e6-96231b3b80d8
Showing
- include/clang/AST/Decl.h 4 additions, 0 deletionsinclude/clang/AST/Decl.h
- include/clang/AST/TypeLoc.h 27 additions, 1 deletioninclude/clang/AST/TypeLoc.h
- lib/AST/Decl.cpp 12 additions, 0 deletionslib/AST/Decl.cpp
- lib/Parse/ParseDeclCXX.cpp 1 addition, 1 deletionlib/Parse/ParseDeclCXX.cpp
- lib/Sema/SemaType.cpp 1 addition, 1 deletionlib/Sema/SemaType.cpp
- lib/Sema/TreeTransform.h 1 addition, 0 deletionslib/Sema/TreeTransform.h
- lib/Serialization/ASTReader.cpp 2 additions, 0 deletionslib/Serialization/ASTReader.cpp
- lib/Serialization/ASTWriter.cpp 1 addition, 0 deletionslib/Serialization/ASTWriter.cpp
- unittests/AST/SourceLocationTest.cpp 67 additions, 0 deletionsunittests/AST/SourceLocationTest.cpp
Loading
Please register or sign in to comment