mirror of https://github.com/google/ormolu.git synced 2024-12-02 10:54:02 +03:00

This is a fork of https://github.com/tweag/ormolu.

Go to file

mrkkrp d61b9101ca Always put parens around kind signatures		2019-07-21 22:43:55 +02:00
.circleci	Clean nix configuration	2019-06-23 19:17:05 +02:00
app	Add an option to tolerate CPP pragmas	2019-07-14 13:14:55 +02:00
data	Always put parens around kind signatures	2019-07-21 22:43:55 +02:00
nix	Drop shebang from the ormolize.sh script	2019-07-15 11:41:45 +02:00
src	Always put parens around kind signatures	2019-07-21 22:43:55 +02:00
tests	Sort language pragmas and fix their placement in modules	2019-07-05 20:03:31 +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	Add nix expression for reformatting sources of arbitrary packages	2019-07-14 13:14:55 +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	Implement rendering of rewrite rule declarations	2019-07-12 17:07:54 +02:00
README.md	Make sure we always get both original and formatted files	2019-07-14 13:14:55 +02:00
Setup.hs	Initial commit	2018-11-25 20:51:22 +07:00
shell.nix	Clean nix configuration	2019-06-23 19:17:05 +02:00

README.md

Ormolu

Ormolu is a formatter for Haskell source code. The project was created with the following features 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:

$ 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.

README.md Unescape Escape