diff options
| author | Raphael Isemann <teemperor@gmail.com> | 2019-11-29 13:02:41 +0100 |
|---|---|---|
| committer | Raphael Isemann <teemperor@gmail.com> | 2019-11-29 13:28:55 +0100 |
| commit | bc7f1df6b61a3c8f88f2541ef9ba73f4ee0ee4fe (patch) | |
| tree | d157ca65af2fc94ab2bb154765fa83f7e93a4628 /lldb/packages/Python/lldbsuite/test/python_api | |
| parent | 363cbcc59040dd337f958fd0fd0584f7c6ebbd63 (diff) | |
| download | bcm5719-llvm-bc7f1df6b61a3c8f88f2541ef9ba73f4ee0ee4fe.tar.gz bcm5719-llvm-bc7f1df6b61a3c8f88f2541ef9ba73f4ee0ee4fe.zip | |
[lldb][NFC] Explicitly ask for a ClangASTContext in ClangASTSource
ClangASTSource currently takes a clang::ASTContext and keeps that
around, but a lot of LLDB's functionality for doing operations
on a clang::ASTContext is in its ClangASTContext twin class. We
currently constantly recompute the respective ClangASTContext
from the clang::ASTContext while we instead could just pass and
store a ClangASTContext in the ClangASTSource. This also allows
us to get rid of a bunch of unreachable error checking for cases
where recomputation fails for some reason.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
