apply-refact: Perform refactorings specified by the refact library.

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

Perform refactorings specified by the refact library. It is primarily used with HLint's --refactor flag.

[Skip to Readme]


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

Versions [RSS],,,,,,,,,,,,,,,,,,,,,
Change log CHANGELOG
Dependencies base (>=4.12 && <4.15), containers (>= && <0.7), directory (>=1.3), extra (>=1.7.3), filemanip (>= && <0.4), filepath, ghc (>=8.6), ghc-boot-th, ghc-exactprint (>=, optparse-applicative (>=, process (>=1.6), refact (>=0.2), syb (>=0.7.1), transformers (>= && <0.6), uniplate (>=1.6.13), unix-compat (>=0.5.2) [details]
License BSD-3-Clause
Author Matthew Pickering
Revised Revision 1 made by zliu41 at 2022-01-02T06:57:39Z
Category Development
Home page
Bug tracker
Source repo head: git clone
Uploaded by zliu41 at 2021-02-24T07:21:01Z
Distributions Arch:, LTSHaskell:, NixOS:, Stackage:
Reverse Dependencies 2 direct, 1 indirect [details]
Executables refactor
Downloads 26091 total (223 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2021-02-24 [all 1 reports]

Readme for apply-refact-

[back to package description]

apply-refact applies refactorings specified by the refact package. It is currently integrated into HLint to enable the automatic application of suggestions.


cabal install apply-refact

Alternatively, clone the repo and run cabal install.

You can also install from Nix:

nix-env -iA nixpkgs.haskellPackages.apply-refact

Executable name is refactor.

Hlint Integration example

hlint src/Main.hs --refactor --refactor-options="--inplace"

Example Usage

# test.hs

foo = (x)

# hlint.refact -- produced by hlint --serialise
[("test.hs:1:7: Warning: Redundant bracket\nFound:\n  (x)\nWhy not:\n
x\n",[Replace {rtype = Expr, pos = SrcSpan {startLine = 1, startCol = 7, endLine
= 1, endCol = 10}, subts = [("x",SrcSpan {startLine = 1, startCol = 8, endLine =
1, endCol = 9})], orig = "x"}])]

> refactor test.hs --refact-file hlint.refact
foo = x

One of either the input file or --refact-file must be specified on the command line. If an input file is specified but not --refact-file then refactor will accept refactorings from stdin and vice versa.

The -i option can be specified to perform the refactoring inplace overwriting the input file. This option is ignored when input is read from stdin.

The -s option can be specified to perform a stepwise evaluation of the refact file. The user is prompted whether to perform each hint before it is performed.

The --pos option is intended to be used by tooling in order to specify which specific hint should be performed.

Multiple -X options may be provided to specify additional default language pragmas which might affect parsing, such as -XLambdaCase or -XRankNTypes.

Refact Files

Refact files should be the result of show on a value of type [(String, [Refactoring SrcSpan])]. The string is a description of the refactoring, one description can have many associated refactoring steps.

Library Structure

The executable is provide so that libraries can use apply-refact without depending on the package. The implementation relies on ghc-exactprint which depends itself on GHC. A transitive dependancy that most developers wish to avoid!

Reporting Bugs

If the program produces a syntactically incorrect result then this is a bug. Please open an issue on the issue tracker with precise instructions about how to reproduce it.

  1. The input file
  2. The refact file
  3. The command used to invoke refactor

There are some known problems with CPP processing. If your library contains CPP directives other than #ifdef it is quite likely that the result will be unexpected.


There are also two hidden flags which can be useful for debugging.


Outputs the GHC AST.


Performs no refactoring operations on the file but is useful to test whether unexpected formatting is due to ghc-exactprint or the refactoring.


Contributions are welcome. You can run the tests via cabal test.