John Ericson 5576d5e987 Parse string context elements properly ... Prior to this change, we had a bunch of ad-hoc string manipulation code scattered around. This made it hard to figure out what data model for string contexts is. Now, we still store string contexts most of the time as encoded strings --- I was wary of the performance implications of changing that --- but whenever we parse them we do so only through the `NixStringContextElem::parse` method, which handles all cases. This creates a data type that is very similar to `DerivedPath` but: - Represents the funky `=<drvpath>` case as properly distinct from the others. - Only encodes a single output, no wildcards and no set, for the "built" case. (I would like to deprecate `=<path>`, after which we are in spitting distance of `DerivedPath` and could maybe get away with fewer types, but that is another topic for another day.)		2023-01-10 13:10:49 -05:00
..
value	Parse string context elements properly	2023-01-10 13:10:49 -05:00
error_traces.cc	Complete genericClosure tests	2022-10-25 01:57:18 +02:00
json.cc	Add unit tests for libexpr (#5377)	2022-05-06 18:05:27 +02:00
libexprtests.hh	Merge pull request #7478 from hercules-ci/make-sure-initNix-called	2023-01-02 14:12:49 +01:00
local.mk	Parse string context elements properly	2023-01-10 13:10:49 -05:00
primops.cc	Merge remote-tracking branch 'origin/master' into coerce-string	2023-01-02 20:53:39 +01:00
trivial.cc	Add unit tests for libexpr (#5377)	2022-05-06 18:05:27 +02:00