ormolu/CHANGELOG.md at 84c2a53349f92ea019e642bc922272198c084454

mirror of https://github.com/ilyakooo0/ormolu.git synced 2024-11-09 15:42:12 +03:00

Mark Karpov 84c2a53349 More compact rendering of type family injectivity constraints

2020-02-01 20:03:41 +01:00

Unreleased

When given several files to format, Ormolu does not stop on the first failure, but tries to format all the files. Issue 502.
Made rendering of pattern matches involving operators consistent with other cases of rendering of operators. Issue 500.
More compact rendering of type family injectivity constraints. Issue 482.

Fixed rendering of record updates with the record dot preprocessor syntax Issue 498.

Fixed an issue related to unnecessary use of curly braces. Issue 473.
Fixed the issue with formatting multi-way if when it happens to be a function applied to arguments Issue 488. This changed the way multi-line if is formatted in general.
Added support for record dot pre-processor when used via the plugin. Issue 486.
Stopped hanging record constructors and improved placing potentially-hanging consturctions in the presence of comments. Issue 447.
Fixed indentation in presence of type applications. Issue 493.
Class and instance declarations now do not have a blank line after where. Grouping of methods from the original input is also preserved with some normalizations. Issue 431.

Switched to ghc-lib-parser instead of depending on the ghc package directly. This should allow us to use newest features of GHC while not necessarily depending on the newest version of the compiler. In addition to that Ormolu is now GHCJS-compatible.
Now unrecognized GHC options passed with --ghc-opt cause Ormolu to fail (exit code 7).
Fixed formatting of result type in closed type families. See issue 420.
Fixed a minor inconsistency between formatting of normal and foreign type signatures. See issue 408.
Fixed a bug when comment before module header with Haddock was moved inside the export list. See issue 430.
Empty foralls are now correctly preserved. See issue 429.
Fixed issue 446, which involved braces and operators.
When there are comments between preceding Haddock (pipe-style) and its corresponding declaration they are preserved like this in the output instead of being shifted. To be clear, this is not a very good idea to have comments in that position because the Haddock will end up not being associated with the declarations. Issues 440 and 448.
Implemented correct handling of shebangs. Issue 377.
Implemented correct handling of stack headers. Issue 393.
Sorting language pragmas cannot not change meaning of the input program anymore. Issue 404.
Fixed formatting of applications where function is a complex expression. Issue 444.