Path to this page:
Next | Query returned 10 messages, browsing 1 to 10 | previous
CVS Commit History:
2023-11-02 07:37:49 by Masatake Daimon | Files touched by this commit (1141) |
Log message:
Revbump all Haskell after updating lang/ghc96
|
2023-10-30 18:10:56 by Masatake Daimon | Files touched by this commit (4) |
Log message:
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
|
2023-10-09 06:55:01 by Masatake Daimon | Files touched by this commit (988) |
Log message:
Bump Haskell packages after updating lang/ghc94
|
2023-01-27 15:35:00 by Masatake Daimon | Files touched by this commit (5) |
Log message:
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
|
2022-09-07 08:50:53 by Masatake Daimon | Files touched by this commit (149) | |
Log message:
Recursive bump for recently updated Haskell packages
|
2022-09-01 11:03:21 by Thomas Klausner | Files touched by this commit (2) |
Log message:
fourmolu: fix build with pkgsrc version of hs-aeson
|
2022-08-20 10:08:24 by Thomas Klausner | Files touched by this commit (211) |
Log message:
hs*: recursive bump for new dependencies needed
for hs-aeson, hs-vector
|
2022-02-26 09:30:14 by Masatake Daimon | Files touched by this commit (1) |
Log message:
devel/fourmolu: Generate shell completion scripts with optparse-applicative
|
2022-02-26 04:58:36 by Masatake Daimon | Files touched by this commit (872) |
Log message:
Bump all Haskell packages after enabling "split sections" in mk/haskell.mk
|
2022-02-16 11:21:51 by Masatake Daimon | Files touched by this commit (6) |
Log message:
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.
|
Next | Query returned 10 messages, browsing 1 to 10 | previous