toml VS dhall

Black uses by default the pyproject.toml file. This file contains a section for each different tool we want to use. The use of a configuration file like pyproject.toml is quite a good choice and helps the contributors to use the same tools and configurations you're using.

> I don't think even though TOML has some official spec

Read it on https://toml.io/ (Full spec on upper-right… with its evolutions up to final 1.00 version).

ini2toml which automatically translates .ini/.cfg files into TOML

toml 1.1 will allow non-ascii in keys (and multi-line inline tables)

See https://github.com/toml-lang/toml/blob/main/CHANGELOG.md

GitHub - toml-lang/toml: Tom's Obvious, Minimal Language

See https://github.com/toml-lang/toml/blob/main/CHANGELOG.md

> I still think it's the best format out there.

What do you think of https://toml.io ?

TOML built-in support

```

If you mean installing Dhall's dependencies (https://github.com/dhall-lang/dhall-haskell/blob/master/dhal...), those aren't too crazy, but they're definitely not all "beginner level". Template Haskell in particular is quite heavyweight.

Ok, lets be specific. Lets write a comment to explain this function:

https://github.com/dhall-lang/dhall-haskell/blob/master/dhal...

I haven't tried it but apparently you can compile to Nix from Dhall:

> You can use this compiler to program Nix using the Dhall language. This package targets people who wish Nix had a type system.

https://github.com/dhall-lang/dhall-haskell/tree/master/dhal...

If the problem is the syntax and people wants some other format that compiles to nix, there's dhall

https://dhall-lang.org/

https://github.com/dhall-lang/dhall-haskell/tree/master/dhal...

https://www.haskellforall.com/2017/01/typed-nix-programming-...

Dhall is a generic config language with some programming capabilities (but not turing complete) that can compile to json, yaml, and other formats, like in this instance nix.

For my GSoC project, I built from scratch the dhall-csv package on the Dhall Haskell implementation Github Repository. Said package provides two executables, dhall-to-csv (which converts Dhall files into CSV files) and csv-to-dhall (which converts CSV files into Dhall files). It also provides Haskell libraries with the functions that translate bidirectionally between Dhall and CSV.

> If you add constraints (like not being able to feed the program to itself as is done in the halting problem and not allowing unbounded loops) then it is possible to determine if a program will terminate or not.

Dhall is a good example - https://github.com/dhall-lang/dhall-haskell .

See also https://dhall-lang.org/

That just seems like an even greater nightmare to me. Soon you would have to learn to read and understand a custom program in a Turing-complete language for each and every installation.

The proper solution is a DSL, just a better DSl. Or perhaps a DSL embedded in something like dhall <https://dhall-lang.org/>, but definitely not a general-purpose programming language.

Dhall