dhall-haskell/dhall
Gabriel Gonzalez 96921f03ab
Fix dhall format to preserve let comments (#1273)
Related to https://github.com/dhall-lang/dhall-haskell/issues/145

Note that this also refactors `Let` to use `Binding` in order
to avoid having to duplicate `Src`-related fields in two
places.
2019-09-04 23:41:44 -05:00
..
benchmark Fix dhall format to preserve let comments (#1273) 2019-09-04 23:41:44 -05:00
dhall Migrate dhall-{bash,json,text} into this repository (#661) 2018-10-28 17:32:51 -07:00
dhall-lang@7639b4ed2f Restore support for records containing both types and terms (#1173) 2019-08-31 13:35:26 -05:00
doctest Fix test errors in windows caused by encoding (#782) 2019-01-16 19:15:57 -08:00
examples Migrate dhall-{bash,json,text} into this repository (#661) 2018-10-28 17:32:51 -07:00
src Fix dhall format to preserve let comments (#1273) 2019-09-04 23:41:44 -05:00
tests Fix dhall format to preserve let comments (#1273) 2019-09-04 23:41:44 -05:00
CHANGELOG.md Fix standard version typo in CHANGELOG (#1180) 2019-08-01 22:44:46 -07:00
default.nix Install mostly static executables on OS X when using Nix (#830) 2019-03-04 19:43:31 -08:00
dhall.cabal Restore support for records containing both types and terms (#1173) 2019-08-31 13:35:26 -05:00
LICENSE Migrate dhall-{bash,json,text} into this repository (#661) 2018-10-28 17:32:51 -07:00
README.md Add a standard-compatibility table (#816) 2019-02-12 10:05:49 -08:00
Setup.hs Migrate dhall-{bash,json,text} into this repository (#661) 2018-10-28 17:32:51 -07:00
shell.nix Migrate dhall-{bash,json,text} into this repository (#661) 2018-10-28 17:32:51 -07:00

dhall

For installation or development instructions, see:

Full documentation here:

Introduction

Dhall is a programmable configuration language that is not Turing-complete

You can think of Dhall as: JSON + functions + types + imports

Motivation

"Why not configure my program using JSON or YAML?"

JSON or YAML are suitable for small configuration files, but larger configuration files with complex schemas require programming language features to reduce repetition. Otherwise, the repetitive configuration files become error-prone and difficult to maintain/migrate.

This post explains in more detail the motivation behind programmable configuration files:

"Why not configure my program using Haskell code?"

You probably don't want to rebuild your program every time you make a configuration change. Recompilation is slow and requires the GHC toolchain to be installed anywhere you want to make configuration changes.

Example

Given this Haskell program saved to example.hs:

-- example.hs

{-# LANGUAGE DeriveGeneric     #-}
{-# LANGUAGE OverloadedStrings #-}

import Dhall

data Example = Example { foo :: Integer, bar :: Vector Double }
    deriving (Generic, Show)

instance Interpret Example

main :: IO ()
main = do
    x <- input auto "./config"
    print (x :: Example)

... which reads in this configuration file:

$ cat ./config
{ foo = 1
, bar = ./bar
}

... which in turn references this other file:

$ cat ./bar
[3.0, 4.0, 5.0]

... you can interpret the Haskell program like this:

$ nix-shell ../nix/test-dhall.nix
[nix-shell]$ runghc example.hs
Example {foo = 1, bar = [3.0,4.0,5.0]}

You can also interpret Dhall programs directly using the installed command-line compiler:

$ dhall
List/head Double ./bar
<Ctrl-D>
Optional Double

Some 3.0

... and you can reference remote expressions or functions by their URL, too:

$ dhall
let null = https://raw.githubusercontent.com/dhall-lang/Prelude/35deff0d41f2bf86c42089c6ca16665537f54d75/List/null
in  null Double ./bar
<Ctrl-D>
Bool

False

Now go read the Dhall tutorial to learn more.

Standard-compatibility table

Haskell package version Supported standard version
1.20.* 5.0.0
1.19.* 4.0.0
1.18.* 3.0.0
1.17.* 2.0.0
1.16.* 1.0.0