7 commits

Author	SHA1	Message	Date
John Ericson	51afea3af2	Never cast FileIngestionMethod to or from boolean	2020-03-30 22:31:51 +00:00
John Ericson	225e62a56a	Replace some bool recursive with a new FileIngestionMethod enum	2020-03-29 15:16:20 -04:00
Eelco Dolstra	d8972317fc	Prevent uninitialized StorePath creation	2020-02-13 16:12:16 +01:00
Eelco Dolstra	d506bd587a	Fix clang warning	2020-01-22 21:20:01 +01:00
Eelco Dolstra	aef635da78	Fix derivation computation with __structuredAttrs and multiple outputs ... 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'	2020-01-21 21:14:13 +01:00
Eelco Dolstra	54bf5ba422	nix-store -r: Handle symlinks to store paths ... Fixes #3270.	2019-12-16 19:11:47 +01:00
Eelco Dolstra	bbe97dff8b	Make the Store API more type-safe ... 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).	2019-12-10 22:06:05 +01:00