This patch replaces the LLDB's JSON implementation with the one from
LLVM in GDBRemoteCommunicationClient.
Details
Details
- Reviewers
labath vsk jasonmolenda clayborg - Commits
- rG2a5a906753d7: [JSON] Use LLVM's library for encoding JSON in GDBRemoteCommunicationClient
rLLDB373498: [JSON] Use LLVM's library for encoding JSON in GDBRemoteCommunicationClient
rL373498: [JSON] Use LLVM's library for encoding JSON in GDBRemoteCommunicationClient
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
LG, though I'm not sure whether using using namespace llvm is such a good idea. There's a fair number of classes with identical names in llvm and lldb_private namespaces. As we start using more of llvm, we will start hitting conflicts. E.g., I've had to handle a bunch of conflicts when I made lldb_private::DataExtractor convertible to llvm::DataExtractor (which made the second name visible nearly everywhere). For this particular case a namespace alias (namespace json = llvm::json) might be a better option.