lix -

Age	Commit message (Collapse)	Author
2021-04-05	Move `StorePathWithOutputs` into its own header/file	John Ericson
	In the following commits it will become less prevalent.
2020-07-13	toStorePath(): Return a StorePath and the suffix	Eelco Dolstra

2020-06-16	Remove StorePath::clone() and related functions	Eelco Dolstra

2020-06-16	StorePath: Rewrite in C++	Eelco Dolstra
	On nix-env -qa -f '<nixpkgs>', this reduces maximum RSS by 20970 KiB and runtime by 0.8%. This is mostly because we're not parsing the hash part as a hash anymore (just validating that it consists of base-32 characters). Also, replace storePathToHash() by StorePath::hashPart().
2020-03-04	nix-build: Fix !<output> handling	Eelco Dolstra
	This was broken by 22a754c091f765061f59bef5ce091268493bb138. https://hydra.nixos.org/eval/1573669
2020-02-28	Fix GC failures on bad store path names	Eelco Dolstra
	It failed on names like '/nix/store/9ip48nkc9rfy0a4yaw98lp6gipqlib1a-'.
2020-01-21	Fix derivation computation with __structuredAttrs and multiple outputs	Eelco Dolstra
	Fixes error: derivation '/nix/store/klivma7r7h5lndb99f7xxmlh5whyayvg-zlib-1.2.11.drv' has incorrect output '/nix/store/fv98nnx5ykgbq8sqabilkgkbc4169q05-zlib-1.2.11-dev', should be '/nix/store/adm7pilzlj3z5k249s8b4wv3scprhzi1-zlib-1.2.11-dev'
2019-12-16	nix-store -r: Handle symlinks to store paths	Eelco Dolstra
	Fixes #3270.
2019-12-10	Make the Store API more type-safe	Eelco Dolstra
	Most functions now take a StorePath argument rather than a Path (which is just an alias for std::string). The StorePath constructor ensures that the path is syntactically correct (i.e. it looks like <store-dir>/<base32-hash>-<name>). Similarly, functions like buildPaths() now take a StorePathWithOutputs, rather than abusing Path by adding a '!<outputs>' suffix. Note that the StorePath type is implemented in Rust. This involves some hackery to allow Rust values to be used directly in C++, via a helper type whose destructor calls the Rust type's drop() function. The main issue is the dynamic nature of C++ move semantics: after we have moved a Rust value, we should not call the drop function on the original value. So when we move a value, we set the original value to bitwise zero, and the destructor only calls drop() if the value is not bitwise zero. This should be sufficient for most types. Also lots of minor cleanups to the C++ API to make it more modern (e.g. using std::optional and std::string_view in some places).