fourmolu: A formatter for Haskell source code

[ bsd3, development, formatting, library, program ] [ Propose Tags ]

A formatter for Haskell source code.


[Skip to Readme]
Versions [faq] 0.0.6.0, 0.1.0.0
Change log CHANGELOG.md
Dependencies aeson (>=1.5.2 && <1.6), base (>=4.12 && <5.0), bytestring (>=0.2 && <0.11), containers (>=0.5 && <0.7), directory (>=1.3.3 && <1.4), dlist (==0.8.*), exceptions (>=0.6 && <0.11), filepath (>=1.4.2.1 && <1.5), fourmolu, ghc-lib-parser (==8.10.*), gitrev (==1.3.*), mtl (>=2.0 && <3.0), optparse-applicative (>=0.14 && <0.16), syb (==0.7.*), text (>=0.2 && <1.3), yaml (>=0.11.2 && <0.12) [details]
License BSD-3-Clause
Author
Maintainer Matt Parsons <parsonsmatt@gmail.com>, George Thomas <georgefsthomas@gmail.com>
Revised Revision 1 made by GeorgeThomas at 2020-08-01T17:01:19Z
Category Development, Formatting
Home page https://github.com/parsonsmatt/fourmolu
Bug tracker https://github.com/parsonsmatt/fourmolu/issues
Source repo head: git clone https://github.com/parsonsmatt/fourmolu.git
Uploaded by GeorgeThomas at 2020-06-23T00:41:39Z
Distributions NixOS:0.1.0.0
Executables fourmolu
Downloads 332 total (129 in the last 30 days)
Rating 1.25 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs uploaded by user
Build status unknown [no reports yet]

Modules

[Index] [Quick Jump]

Flags

NameDescriptionDefaultType
dev

Turn on development settings.

DisabledManual

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

For package maintainers and hackage trustees


Readme for fourmolu-0.1.0.0

[back to package description]

~~Ormolu~~ Fourmolu

License BSD3 Hackage Stackage Nightly Stackage LTS Build status

~~Ormolu~~ Fourmolu 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 influences 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.
  • Implementing one “true” formatting style ~~which admits no configuration~~ requires you to fork the project to configure it (TODO: add a config file).
  • That formatting style aims to result in minimal diffs while still remaining very close to “conventional” Haskell formatting people use.
  • Choose a style compatible with modern dialects of Haskell. As new Haskell extensions enter broad use, we may change the style to accomodate them.
  • Idempotence: 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 -A ormolu

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-14.3
packages:
- '.'

$ stack build

To use Ormolu directly from GitHub with Nix, this snippet may come in handy:

# This overlay adds Ormolu straight from GitHub.
self: super:

let source = super.fetchFromGitHub {
      owner = "tweag";
      repo = "ormolu";
      rev = "de279d80122b287374d4ed87c7b630db1f157642"; # update as necessary
      sha256 = "0qrxfk62ww6b60ha9sqcgl4nb2n5fhf66a65wszjngwkybwlzmrv"; # as well
    };
    ormolu = import source { pkgs = self; };
in {
  haskell = super.haskell // {
    packages = super.haskell.packages // {
      "${ormolu.ormoluCompiler}" = super.haskell.packages.${ormolu.ormoluCompiler}.override {
        overrides = ormolu.ormoluOverlay;
      };
    };
  };
}

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

Use find to format a tree recursively:

$ ormolu --mode inplace $(find . -name '*.hs')

Magic comments

Ormolu understands two magic comments:

{- ORMOLU_DISABLE -}

and

{- ORMOLU_ENABLE -}

This allows us to disable formatting selectively for code between these markers or disable it for the entire file. To achieve the latter, just put {- ORMOLU_DISABLE -} at the very top. Note that the source code should still be parseable even without the “excluded” part. Because of that the magic comments cannot be placed arbitrary, but should rather enclose independent top-level definitions.

Current limitations

  • CPP support is experimental. CPP is virtually impossible to handle correctly, so we process them as a sort of unchangeable snippets. This works only in simple cases when CPP conditionals surround top-level declarations. See the CPP section in the design notes for a discussion of the dangers.
  • Input modules should be parsable by Haddock, which is a bit stricter criterion than just being valid Haskell modules.
  • Various minor idempotence issues, most of them are related to comments.

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 the root of the cloned 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 © 2018–present Tweag I/O