Viktor Kleen

You will probably need to write a function that takes your configuration data and processes it into a form understood by ansible. And then put that into a recursive record...

Just from a syntax perspective, this makes me wonder if we would want to permit `{ _ = ... }` as a dictionary contract. For normal records, a default value...

A minimal step towards this could be putting `Assert` and `check` from `tests/integration/pass/lib/assert.ncl` into a stdlib namespace, e.g. `std.tests`. That seems to be all the Nickel specific functionality we have...

If I understand correctly, `funflow` will fail to build with new versions of `unix-compat` because the latter removed `Sytem.PosixCompat.User` which our Docker support is using. But the latter has always...

Personally, I like the approach. The extra indirection through an import should be entirely inconsequential. I don't see a good reason why tests couldn't be made to work with this...

I have a feeling that that should be fixed by using `nativeBuildInputs` instead of `buildInputs`. Can you try that?

We can't build a fully statically built binary on darwin at all, that's just not a thing that OS X supports. But we should be able to build one that...