-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dhall-nix? #75
Comments
@MichaelXavier: You don't need to add an additional build process. There is a Note that it's restricted to an older version of That said, I haven't made a serious attempt to use |
Thanks for the quick response, @Gabriel439. I'm curious if you have any doubts about its usability as a replacement. Maybe when you get used to the nix syntax and error messages, that particular downside to the nix expression language isn't a big enough problem to bother with? |
@MichaelXavier: The main issue is that Nixpkgs depends heavily on weakly-typed idioms and general recursion which you can't embed in Dhall. So you can carve out some strongly-typed islands using Dhall, but you'll hit a wall pretty quickly. I think a slightly more promising approach is https://github.com/dhallix which is basically an attempt to redo something like Nixpkgs except in a way more idiomatic to Dhall, but that requires significant performance improvements to the interpreter to be realistic |
@Gabriel439 thanks! All of that makes sense. I've got a few more hours under my belt with dhall and started to see where nix exceeds the functionality that dhall limits itself to or how performance could be an issue when you're evaluating huge expressions. |
You're welcome! 🙂 |
@Gabriel439 |
@cvoges12: This will be fixed in the next release (~ 1 week from now). See: dhall-lang/dhall-haskell#1000 |
This may be more of a question than an issue. I noticed in the main README you mention that nix has worse error messages and that is owed to not having a type system. I'm wondering if you have used dhall-nix to address this. The syntax is so similar that it doesn't seem like it would add much overhead in terms of noise. Is the problem that you'd need to layer a build process (make?) over the whole project to convert your source-controlled dhall expressions into git-ignored nix expressions?
The text was updated successfully, but these errors were encountered: