1
1
mirror of https://github.com/google/ormolu.git synced 2024-11-27 13:13:23 +03:00
Go to file
2019-08-28 15:05:53 +02:00
.circleci Clean nix configuration 2019-06-23 19:17:05 +02:00
app Support formatting multiple files at once 2019-08-16 23:06:05 +02:00
data Make multi-line multi-name patterns prettier 2019-08-28 12:04:25 +02:00
nix Implement the --check-idempotency flag 2019-08-16 22:21:20 +02:00
src Make multi-line multi-name patterns prettier 2019-08-28 12:04:25 +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 the contribution guidelines 2019-08-28 15:05:53 +02:00
default.nix Adjust the nix expression to facilitate importing from outside 2019-08-16 17:49:57 +02:00
DESIGN.md Add examples to table of contents and drop the roadmap 2019-08-21 12:31:02 +02:00
LICENSE.md Replace current year with the word "present" 2019-07-02 21:27:45 +02:00
ormolu.cabal Update the ‘data-files’ field in Cabal file 2019-08-28 13:55:44 +02:00
README.md Update the readme mentioning current limitations 2019-08-28 15:02:10 +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

Current limitations

  • Does not handle CPP (wontfix, see the design document).
  • Ormolu knows nothing about operator precedence so complex chains of operators may be rendered in slightly unpleasant ways †.
  • Various minor idempotence issues, most of them are related to comments †.

† To be resolved in 0.0.2.0.

Editor integration

We know of the following editor integrations:

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