CVS log for pkgsrc/devel/fourmolu/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / devel / fourmolu

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

recursive revbump after patching lang/ghc910

Bump all Haskell packages after switching the default compiler.

devel/fourmolu: update to fourmolu-0.17.0.0

## Fourmolu 0.17.0.0

* Add new `import-grouping` option to group imports with grouping rules specified in configuration ([#403](https://github.com/fourmolu/fourmolu/pull/403))

* Add new `sort-constraints` option to sort constraints alphabetically ([#433](https://github.com/fourmolu/fourmolu/pull/433))

* Add new `sort-derived-classes` option to sort classes in deriving clauses ([#434](https://github.com/fourmolu/fourmolu/pull/434))

* Add new `sort-derived-clauses` option to sort classes deriving clauses ([#434](https://github.com/fourmolu/fourmolu/pull/434))

* Add new `trailing-section-operators` option to disable trailing "section" operators (those that are `infixr 0`, such as `$`) ([#444](https://github.com/fourmolu/fourmolu/pull/444))

* Fix issue where `single-constraint-parens: never` would drop parentheses around implicit parameters ([#446](https://github.com/fourmolu/fourmolu/issues/446))

* Fix indentation for parenthesized expressions that start off the indentation column ([#428](https://github.com/fourmolu/fourmolu/issues/428))

* Allow multiline comments in indented contexts ([#65](https://github.com/fourmolu/fourmolu/issues/65))


## Fourmolu 0.16.2.0

### Upstream changes:

#### Ormolu 0.7.7.0

* Use single-line layout for parens around single-line content. [Issue
  1120](https://github.com/tweag/ormolu/issues/1120).

* Allow function arguments to be on the same line even if the full type
  (with constraints and foralls) are on multiple lines. [PR
  1125](https://github.com/tweag/ormolu/pull/1125).

## Fourmolu 0.16.1.0

### Upstream changes:

#### Ormolu 0.7.6.0

* Fix Haddock comments on infix constructors
  [Issue 758](https://github.com/tweag/ormolu/issues/758).

* Don't require a trailing newline in `.ormolu` files. [Issue
  1122](https://github.com/tweag/ormolu/issues/1122).

* Remove unnecessary indentation from list comprehensions. [Issue
  966](https://github.com/tweag/ormolu/issues/966).

## Fourmolu 0.16.0.0

* Allow specifying path to configuration file with `--config` ([#396](https://github.com/fourmolu/fourmolu/issues/396))

### Upstream changes:

#### Ormolu 0.7.5.0

* Switched to `ghc-lib-parser-9.10`, with the following new syntactic features/behaviors:
  * GHC proposal [#575](https://github.com/ghc-proposals/ghc-proposals/blob/10290a668608d608c3f6c6010be265cf7a02e1fc/proposals/0575-deprecated-instances.rst): deprecated instances.
  * GHC proposal [#281](https://github.com/ghc-proposals/ghc-proposals/blob/10290a668608d608c3f6c6010be265cf7a02e1fc/proposals/0281-visible-forall.rst): visible forall in types of terms.
    Enabled by `RequiredTypeArguments` (enabled by default).
  * `LinearTypes`: `let` and `where` bindings can now be linear, in particular have multiplicity annotations.
  * Using `forall` as an identifier is now a parse error.
  * GHC proposal [#65](https://github.com/ghc-proposals/ghc-proposals/blob/10290a668608d608c3f6c6010be265cf7a02e1fc/proposals/0065-type-infix.rst): namespacing fixity declarations for type names and WARNING/DEPRECATED pragmas.
  * `TypeAbstractions` now supports `@`-binders in lambdas and function equations.
  * Support for the `GHC2024` language.

* Updated to `Cabal-syntax-3.12`.

Recursive revbump after changing the default Haskell compiler

devel/fourmolu: Update to 0.15.0.0

Fourmolu 0.15.0.0
    * Add single-deriving-parens configuration option to determine if
      deriving clauses of a single type should be parenthesized (#386)
    * Fix the order in which the configurations are applied (#390)

Upstream changes:
Ormolu 0.7.4.0
    * Don't error when the JavaScriptFFI language pragma is present. Issue
      1087.
    * Improve comment placement in if-then-else blocks. Issue 998.
    * Now command line options for fixity overrides and module re-exports
      overwrite information from .ormolu files. Issue 1030.
    * Respect newlines in data declarations in more cases. Issue 1077 and
      issue 947.
    * The -d / --debug command line option now makes Ormolu print out debug
      information regarding operator fixity inference. Issue 1060.

Revbump all Haskell after updating lang/ghc96

devel/fourmolu: Update to 0.14.1.0

The change log is too long to paste here. See
https://hackage.haskell.org/package/fourmolu-0.14.1.0/changelog

Bump Haskell packages after updating lang/ghc94

revbump all the Haskell packages after modifying the runtime system of lang/ghc94

devel/fourmolu: Update to 0.10.1.0

The release note is too long to paste here. See
https://hackage.haskell.org/package/fourmolu-0.10.1.0/changelog

Recursive bump for recently updated Haskell packages

hs*: recursive bump for new dependencies needed

for hs-aeson, hs-vector

devel/fourmolu: Generate shell completion scripts with optparse-applicative

Bump all Haskell packages after enabling "split sections" in mk/haskell.mk

devel/fourmolu: import fourmolu-0.5.0.1

Fourmolu is a formatter for Haskell source code. It is a fork of Ormolu,
with the intention to continue to merge upstream improvements.

We share all bar one of Ormolu's goals:

* 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 certain situations 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.
* That formatting style aims to result in minimal diffs.
* Choose a style compatible with modern dialects of Haskell. As new Haskell
  extensions enter broad use, we may change the style to accommodate them.
* Idempotence: formatting already formatted code doesn't change it.
* Be well-tested and robust so that the formatter can be used in large
  projects.
* We allow configuration of various parameters, via CLI options or config
  files. We encourage any contributions which add further flexibility.