7 commits

Author	SHA1	Message	Date
Eelco Dolstra	ee235e764c	Merge branch 'libarchive' of https://github.com/yorickvP/nix	2019-12-19 14:47:18 +01:00
Eelco Dolstra	ac9cc2ec08	Move some code	2019-12-13 19:10:39 +01:00
Eelco Dolstra	b4edc3ca61	Don't leak exceptions	2019-12-13 19:05:26 +01:00
Eelco Dolstra	ca87707c90	Get rid of CBox	2019-12-13 19:05:26 +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
Eelco Dolstra	949dc84894	Fix segfault on i686-linux ... https://hydra.nixos.org/build/107467517 Seems that on i686-linux, gcc and rustc disagree on how to return 1-word structs: gcc has the caller pass a pointer to the result, while rustc has the callee return the result in a register. Work around this by using a bare pointer.	2019-11-27 14:17:15 +01:00
Eelco Dolstra	b7fba16613	Move code around	2019-11-26 22:07:28 +01:00