Go to file
2018-04-11 17:41:57 -07:00
benchmarks tests for comment parsing and parser benchmarks 2014-08-27 23:54:31 +02:00
data Use version of nix that has eval-okay-regex-split.exp 2018-04-10 12:33:31 -07:00
doc Add the C++ parser as documentation 2014-07-04 01:55:27 -05:00
main Add testing code for writing out Nix parses as compact regions 2018-04-11 14:35:17 -07:00
src Update evalWith in Lint.hs 2018-04-11 17:41:57 -07:00
tests Use hnix to process nixpkgs in the tests 2018-04-11 13:56:31 -07:00
.gitignore Add some things to .gitignore 2018-03-30 13:07:40 -04:00
.gitmodules Update submodule reference 2018-04-10 12:33:51 -07:00
.travis.yml Enable nixpkgs parsing test on Travis 2018-04-10 11:44:41 -07:00
default.nix Minor simplification in default.nix 2018-04-10 12:56:20 -07:00
hnix.cabal Add testing code for writing out Nix parses as compact regions 2018-04-11 14:35:17 -07:00
LICENSE Change LICENSE to BSD3 2016-12-18 17:10:06 -08:00
Makefile Merge {build,shell,default}.nix into default.nix 2018-01-28 21:58:33 +00:00
package.yaml Add testing code for writing out Nix parses as compact regions 2018-04-11 14:35:17 -07:00
README.md Add note about how to profile hnix 2018-04-10 11:49:18 -07:00
Setup.hs Setup cabal file, fix all warnings 2014-06-30 22:37:20 -05:00

hnix

Haskell parser, evaluator and type checker for the Nix language.

Prerequisites

Nix is installed and in your $PATH. This is so that nix-store can be used for interacting with store paths, until hnix-store is ready.

Getting Started

$ git clone https://github.com/jwiegley/hnix.git
...
$ cd hnix
$ cabal2nix --shell . > default.nix
$ nix-shell
...
$ cabal test
...
$ cabal bench
...
$ ./dist/build/hnix/hnix --help

Building with profiling enabled

To build hnix with profiling enabled:

$ nix-shell --arg doProfiling true
$ cabal configure --enable-tests --enable-profiling
$ ./dist/build/hnix/hnix <args> +RTS -p

How you can help

If you're looking for a way to help out, try taking a look here. When you find an issue that looks interesting to you, comment on the ticket to let others know you're working on it; look for others who might have done the same. You can talk with everyone live on gitter.

When you're ready to submit a pull request, test it with:

git submodule update --init --recursive
nix-shell --run "LANGUAGE_TESTS=yes cabal test"

Make sure that all the tests that were passing prior to your PR are still passing afterwards; it's OK if no new tests are passing.