1
1
mirror of https://github.com/google/ormolu.git synced 2024-11-27 13:13:23 +03:00
Go to file
mrkkrp f94400b486 Indent ‘then’ and ‘else’ clauses one level further
This arguably improves readability especially when if-then-else is placed
inside of a ‘do’-block.
2019-08-16 22:38:38 +02:00
.circleci Clean nix configuration 2019-06-23 19:17:05 +02:00
app Implement the --check-idempotency flag 2019-08-16 22:21:20 +02:00
data Indent ‘then’ and ‘else’ clauses one level further 2019-08-16 22:38:38 +02:00
nix Implement the --check-idempotency flag 2019-08-16 22:21:20 +02:00
src Indent ‘then’ and ‘else’ clauses one level further 2019-08-16 22:38:38 +02:00
tests Misc corrections 2019-08-11 16:04:42 +02:00
.gitignore Clean nix configuration 2019-06-23 19:17:05 +02:00
CHANGELOG.md Initial commit 2018-11-25 20:51:22 +07:00
CONTRIBUTING.md Update ‘CONTRIBUTING.md’ 2019-07-13 21:51:45 +02:00
default.nix Adjust the nix expression to facilitate importing from outside 2019-08-16 17:49:57 +02:00
DESIGN.md Minor corrections to the design document 2019-02-14 22:12:13 +01:00
LICENSE.md Replace current year with the word "present" 2019-07-02 21:27:45 +02:00
ormolu.cabal Update cabal file to include the full list of data sub-dirs 2019-08-16 17:29:02 +02:00
README.md A couple of minor corrections to the readme 2019-08-04 21:20:30 +02:00
Setup.hs Initial commit 2018-11-25 20:51:22 +07:00
shell.nix Adjust the nix expression to facilitate importing from outside 2019-08-16 17:49:57 +02:00

Ormolu

CircleCI

Ormolu is a formatter for Haskell source code. The project was created with the following goals in mind:

  • Using GHC's own parser to avoid parsing problems caused by haskell-src-exts.
  • Let some whitespace be programmable. The layout of the input influence the layout choices in the output. This means that the choices between single-line/multi-line layouts in each particular situation are made by the user, not by an algorithm. This makes the implementation simpler and leaves some control to the user while still guaranteeing that the formatted code is stylistically consistent.
  • Writing code in such a way so it's easy to modify and maintain. Roughly, it means that the project follows the path of hindent and is very much about printing AST in a particular way.
  • Implementing one “true” formatting style which admits no configuration.
  • That formatting style aims to result in minimal diffs while still remaining very close to “conventional” Haskell formatting people use.
  • Idempotency: formatting already formatted code doesn't change it.
  • Be well-tested and robust to the point that it can be used in large projects without exposing unfortunate, disappointing bugs here and there.

Building

The easiest way to build the project is with Nix:

$ nix-build

Or with cabal-install from the Nix shell:

$ nix-shell --run "cabal new-build"

Alternatively, stack could be used with a stack.yaml file as follows.

$ cat stack.yaml
resolver: lts-13.19
packages:
- '.'

$ stack build

Usage

The following will print the formatted output to the standard output.

$ ormolu Module.hs

Add --mode inplace to replace the contents of the input file with the formatted output.

$ ormolu --mode inplace Module.hs

Running on Hackage

It's possible to try Ormolu on arbitrary packages from Hackage. For that execute (from root of clonned repo):

$ nix-build -A hackage.<package>

Then inspect result/log.txt for possible problems. The derivation will also contain formatted .hs files for inspection and original inputs with .hs-original extension (those are with CPP dropped, exactly what is fed into Ormolu).

Contributing

See CONTRIBUTING.md.

License

See LICENSE.md.

Copyright © 2018present Tweag I/O