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
..
local.mk	Parse string context elements properly	2023-01-10 13:10:49 -05:00
plugintest.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00