dhall-haskell/dhall
Gabriel Gonzalez 3f2c42014f
Simplify dhall version output to just version string (#1163)
The motivation for this is two-fold:

* To get rid of the standard version from the output

  Currently it's just "None", which could be fixed, but keeping it up to
  date is error-prone, so I prefer to just remove it.

* To make the output machine-readable

Example:

```
$ dhall version
1.24.0
```
2019-07-28 20:44:30 -07:00
..
benchmark Preparing Dhall.Import for "Semi-semantic" caching (#1113) 2019-07-17 15:20:48 +00:00
dhall Migrate dhall-{bash,json,text} into this repository (#661) 2018-10-28 17:32:51 -07:00
dhall-lang@f4ee1fb8f8 Enable the fixed potPourri test (#1144) 2019-07-21 15:21:20 +02: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 Simplify dhall version output to just version string (#1163) 2019-07-28 20:44:30 -07:00
tests Fix tests without with-http flag (#1159) 2019-07-27 02:59:25 +00:00
CHANGELOG.md Version 1.23.0 → 1.24.0 (#984) 2019-06-06 17:14:43 -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 Fix tests without with-http flag (#1159) 2019-07-27 02:59:25 +00: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