summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-10-02 18:02:36 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-10-02 18:02:36 +0000
commit2a0c8b1143225feeae87eff3a963491b14f06daf (patch)
tree0827c4961c660b8158f1da960f1d523b65324d1f /lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
parent4f8151e62ef1a85929fe241fda3360163135e55a (diff)
downloadbcm5719-llvm-2a0c8b1143225feeae87eff3a963491b14f06daf.tar.gz
bcm5719-llvm-2a0c8b1143225feeae87eff3a963491b14f06daf.zip
[JSON] Remove Utility/JSON.{h|cpp}
This patch is the final step in my quest to get rid of the JSON parser in LLDB. Vedant's coverage report [1] shows that it was mostly untested. Furthermore, the LLVM implementation has a much nicer API and using it means one less thing to maintain for LLDB. [1] http://lab.llvm.org:8080/coverage/coverage-reports/index.html Differential revision: https://reviews.llvm.org/D68305 llvm-svn: 373501
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud