[llvm-dev] RFC: Adding a JSON library to LLVM Support

[Pavel Labath via llvm-dev]

LLDB has a JSON parser/serializer that we'd like to get rid of. The
main thing that's missing from YamlIO for us to do that is the ability
to handle (or at very least, not choke on) unknown keys (for example,
keys that are only generated by an lldb-server from the future --
backwards/forwards compatibility).

On 27 October 2017 at 12:53, Sam McCall via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> We don't have a dedicated JSON library in the LLVM tree, I'd like to add
> one. The pressing need is for clangd, but we have other tools that
> read/write JSON too.
>
> I'm proposing we write a new one, rather than importing a third-party
> library (licensing/integration reasons), on or extending YamlParser/YamlIO
> (usability/flexibility). I lean towards a design that parses a full DOM at
> once, and provides literal-like syntax for composing documents.
>
> I've written a document laying out the reasons for taking this path, and my
> proposal for a design (with links to a prototype)
> https://docs.google.com/document/d/1OEF9IauWwNuSigZzvvbjc1cVS1uGHRyGTXaoy3DjqM4/edit
> (Comments are enabled, but high-level discussion probably belongs on the
> list instead.)
>
> What do you think? I'm particularly interested in which parts of LLVM
> produce/consume JSON (or might want to), and what they need. I'm mostly
> familiar with the stuff in clang-tools-extra.
>
> Cheers, Sam
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>