aboutsummaryrefslogtreecommitdiff
path: root/nix-rust/src/store
AgeCommit message (Collapse)Author
2020-02-10Remove macro_useLeonhard Markert
As of Rust 2018, macro_use is no longer required in most circumstances. I think it is generally a good idea to remove these when not needed, to stop them from polluting the crate's global namespace. https://doc.rust-lang.org/edition-guide/rust-2018/macros/macro-changes.html#macro_rules-style-macros
2019-12-16StorePath::new(): Check store directoryEelco Dolstra
2019-12-10Speed up StorePath::to_string()Eelco Dolstra
1.81% -> 0.56%
2019-12-10Make the Store API more type-safeEelco 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).
2019-12-10Add StorePath testsEelco Dolstra
2019-12-10Shut up warningsEelco Dolstra
2019-12-10Use hyper directly instead of reqwestEelco Dolstra
2019-12-10Update to async/await-enabled tokioEelco Dolstra
2019-12-10StorePath improvementsEelco Dolstra
2019-12-10Add base32 encoder/decoderEelco Dolstra
2019-12-10Move stuff aroundEelco Dolstra