There is no point in separately checking lt/eq/gt separately when we always need the full ordering anyway. Change-Id: I993108029d205ac17f01acdb6dbf9b2f0cd80f28 Reviewed-on: https://cl.snix.dev/c/snix/+/30372 Reviewed-by: Florian Klink <flokli@flokli.de> Tested-by: besadii |
||
|---|---|---|
| .. | ||
| benches | ||
| builtin-macros | ||
| proptest-regressions/value | ||
| src | ||
| tests | ||
| .skip-subtree | ||
| build.rs | ||
| Cargo.toml | ||
| clippy.toml | ||
| default.nix | ||
| README.md | ||
Snix Evaluator
This project implements an interpreter for the Nix programming language. You can experiment with an online version of the evaluator: snixbolt.
The interpreter aims to be compatible with nixpkgs, on the
foundation of Nix 2.3.
Important note: The evaluator is not yet feature-complete, and while the core mechanisms (compiler, runtime, ...) have stabilised somewhat, a lot of components are still changing rapidly.
Tests
Snix currently has three language test suites for snix-eval:
-
nix_testsandsnix_testsare based on the same mechanism borrowed from the C++ Nix implementation. They consist of Nix files as well as expected output (if applicable). The test cases are split into four categories:eval-okay(evaluates successfully with the expected output),eval-fail(fails to evaluate, no expected output),parse-okay(expression parses successfully, no expected output) andparse-fail(expression fails to parse, no expected output). Snix currently ignores the last two types of test cases, since it doesn't implement its own parser.Both test suites have a
notyetpassingdirectory. All test cases in here test behavior that is not yet supported by Snix. They are considered to be expected failures, so you can't forget to move them into the test suite proper when fixing the incompatibility.Additionally, separate targets in the depot pipeline, under
//snix/verify-lang-tests, check both test suites (includingnotyetpassingdirectories) against C++ Nix 2.3 and the default C++ Nix version in nixpkgs. This way we can prevent accidentally introducing test cases for behavior that C++ Nix doesn't exhibit.-
nix_testshas the test cases from C++ Nix's language test suite and is sporadically updated by manually syncing the directories. Thenotyetpassingdirectory shows how far it is until we pass it completely. -
snix_testscontains test cases written by the Snix contributors. Some more or less duplicate test cases contained innix_tests, but many cover relevant behavior that isn't bynix_tests. Consequently, it'd be nice to eventually merge the two test suites into a jointly maintained, common Nix language test suite.It also has a
notyetpassingdirectory for missing behavior that is discovered while working on Snix and isn't covered by thenix_testssuite.
-
-
nix_oraclecan evaluate Nix expressions in Snix and compare the result against C++ Nix (2.3) directly. Eventually it should gain the ability to property test generated Nix expressions. An additional feature is that it can evaluate expressions without--strict, so thunking behavior can be verified more easily.
rnix-parser
Snix is written in memory of jD91mZM2, the author of rnix-parser who sadly passed away.
Snix makes heavy use of rnix-parser in its bytecode compiler. The parser is now maintained by Nix community members.