John Ericson 204749270b JSON alongside binary proto serialization test data ... This makes the proto serializer characterisation test data be accompanied by JSON data. This is arguably useful for a reasons: - The JSON data is human-readable while the binary data is not, so it provides some indication of what the test data means beyond the C++ literals. - The JSON data is language-agnostic, and so can be used to quickly rig up tests for implementation in other languages, without having source code literals at all (just go back and forth between the JSON and the binary). - Even though we have no concrete plans to place the binary protocol 1-1 or with JSON, it is still nice to ensure that the JSON serializers and binary protocols have (near) equal coverage over data types, to help ensure we didn't forget a JSON (de)serializer.		2025-11-10 18:32:31 -05:00
..
include/nix/util/tests	JSON alongside binary proto serialization test data	2025-11-10 18:32:31 -05:00
.version	Move unit tests to the location Meson expects them to be	2024-10-17 15:42:16 -04:00
hash.cc	treewide: Bump C++ standard version to C++23	2025-08-19 15:33:27 +03:00
meson.build	meson: Move asan-options to common	2025-10-11 16:08:35 +03:00
nix-meson-build-support	rename: build-utils-meson -> nix-meson-build-support	2024-12-09 16:54:42 +01:00
package.nix	Expose the nix component in header include paths	2025-04-01 11:40:42 -04:00
string_callback.cc	Apply clang-format universally.	2025-07-18 12:47:27 -04:00