John Ericson ee420ac64e Legacy vs non-legacy to_string/parse for DerivedPath ... As requested by @roberth, it is good to call out the specific instances we care about, which is `!` for the RPC protocols, and `^` for humans. This doesn't take advantage of parametricity as much, but since the human and computer interfaces are good to decouple anyways (we don't care if they drift further apart over time in the slightest) some separation and slight duplication is fine. Also, unit test both round trips.		2023-04-14 20:45:11 -04:00
..
test-data	Add error reporting to machine spec paser	2021-10-17 12:45:56 +04:00
derivation.cc	Include the name in the JSON for derivations	2023-04-07 08:34:58 -04:00
derived-path.cc	Legacy vs non-legacy to_string/parse for DerivedPath	2023-04-14 20:45:11 -04:00
derived-path.hh	Ensure all headers have #pragma once and are in API docs	2023-03-31 23:19:44 -04:00
libstore.hh	Ensure all headers have #pragma once and are in API docs	2023-03-31 23:19:44 -04:00
local.mk	More property tests	2023-01-29 17:09:59 -05:00
machines.cc	Add error reporting to machine spec paser	2021-10-17 12:45:56 +04:00
nar-info-disk-cache.cc	NarInfoDiskCache: Also test id consistency with updated fields	2023-02-07 23:34:36 +01:00
outputs-spec.cc	More property tests	2023-01-29 17:09:59 -05:00
outputs-spec.hh	Ensure all headers have #pragma once and are in API docs	2023-03-31 23:19:44 -04:00
path.cc	More property tests	2023-01-29 17:09:59 -05:00
path.hh	Ensure all headers have #pragma once and are in API docs	2023-03-31 23:19:44 -04:00
references.cc	Add a test for RefScanSink and clean up the code	2021-10-04 14:29:42 +02:00