nix-super/src/libexpr/value-to-json.hh

#pragma once

#include "nixexpr.hh"
#include "eval.hh"

#include <string>
#include <map>

namespace nix {

class JSONPlaceholder;

void printValueAsJSON(EvalState & state, bool strict,
    Value & v, const PosIdx pos, JSONPlaceholder & out, PathSet & context);

void printValueAsJSON(EvalState & state, bool strict,
    Value & v, const PosIdx pos, std::ostream & str, PathSet & context);

}
Add a toJSON primop 2013-11-19 01:03:11 +02:00			`#pragma once`

			`#include "nixexpr.hh"`
			`#include "eval.hh"`

			`#include <string>`
			`#include <map>`

			`namespace nix {`

nix path-info: Add --json flag Also, factor out JSON generation from value-to-json.{cc,hh}, and support producing indented JSON. 2016-08-26 19:55:55 +03:00			`class JSONPlaceholder;`
Refactor JSON output 2013-11-19 01:33:06 +02:00
nix path-info: Add --json flag Also, factor out JSON generation from value-to-json.{cc,hh}, and support producing indented JSON. 2016-08-26 19:55:55 +03:00			`void printValueAsJSON(EvalState & state, bool strict,`
replace most Pos objects/ptrs with indexes into a position table Pos objects are somewhat wasteful as they duplicate the origin file name and input type for each object. on files that produce more than one Pos when parsed this a sizeable waste of memory (one pointer per Pos). the same goes for ptr<Pos> on 64 bit machines: parsing enough source to require 8 bytes to locate a position would need at least 8GB of input and 64GB of expression memory. it's not likely that we'll hit that any time soon, so we can use a uint32_t index to locate positions instead. 2022-03-04 20:31:59 +02:00			`Value & v, const PosIdx pos, JSONPlaceholder & out, PathSet & context);`
Refactor JSON output 2013-11-19 01:33:06 +02:00
nix path-info: Add --json flag Also, factor out JSON generation from value-to-json.{cc,hh}, and support producing indented JSON. 2016-08-26 19:55:55 +03:00			`void printValueAsJSON(EvalState & state, bool strict,`
replace most Pos objects/ptrs with indexes into a position table Pos objects are somewhat wasteful as they duplicate the origin file name and input type for each object. on files that produce more than one Pos when parsed this a sizeable waste of memory (one pointer per Pos). the same goes for ptr<Pos> on 64 bit machines: parsing enough source to require 8 bytes to locate a position would need at least 8GB of input and 64GB of expression memory. it's not likely that we'll hit that any time soon, so we can use a uint32_t index to locate positions instead. 2022-03-04 20:31:59 +02:00			`Value & v, const PosIdx pos, std::ostream & str, PathSet & context);`
Refactor JSON output 2013-11-19 01:33:06 +02:00
Add a toJSON primop 2013-11-19 01:03:11 +02:00			`}`