Sam McCall 73b822e520 [JSON] Facility to track position within an object and report errors. ... This error model should be rich enough for most applications. It comprises: - a name for the root object, so the user knows what we're parsing - a path from the root object to the JSON node most associated with the error - a local error message This can be presented as an llvm::Error e.g. "expected string at ConfigFile.credentials[0].username" It's designed to be cheap: Paths are a linked list of lightweight objects on the stack. No heap allocations unless errors are encountered. A subsequent commit will make use of this in the JSON-to-object translation facilities: fromJSON and ObjectMapper. However it's independent of these and can be used for e.g. validation alone. Another subsequent commit will support showing the error in its context within the parsed value. Differential Revision: https://reviews.llvm.org/D88103		2020-09-24 00:09:09 +02:00
..
llvm	[JSON] Facility to track position within an object and report errors.	2020-09-24 00:09:09 +02:00
llvm-c	[ORC] Add operations to create and lookup JITDylibs to OrcV2 C bindings.	2020-09-16 13:49:30 -07:00