@@ -37,8 +37,8 @@ along with its context -- eg whatever is available in the GitHub PR interface.
37
37
As long that rendering doesn't show that the PR spoils something like
38
38
intentional alignment for example, then the PR has no style problems.
39
39
40
- We run ` stylish-haskell ` as a requirement for merging. The specific
41
- configuration can be found [ here] [ stylish -config] .
40
+ We run ` fourmolu ` as a requirement for merging. The specific
41
+ configuration can be found [ here] [ fourmolu -config] .
42
42
43
43
## Guiding principles
44
44
@@ -871,8 +871,8 @@ the rules below, it is good practice to update the code's style to match them.
871
871
872
872
* Why :* to avoid wasting horizontal screen space.
873
873
874
- 15 . __Import lists__: we use `stylish - haskell ` to automatically format import
875
- lists. See the [`. stylish - haskell . yaml` config][stylish - config].
874
+ 15 . __Import lists__: we use `fourmolu ` to automatically format import
875
+ lists. See the [`fourmolu . yaml` config][fourmolu - config].
876
876
877
877
When importing modules from consensus and in particular modules from the
878
878
same package, an import list and a qualifier can be omitted. For example,
@@ -882,8 +882,8 @@ the rules below, it is good practice to update the code's style to match them.
882
882
When importing from other packages, we prefer to use either an import list
883
883
or a qualifier.
884
884
885
- 16 . __Export lists__: we use `stylish - haskell ` to automatically format export
886
- lists. See the [`. stylish - haskell . yaml` config][stylish - config]. We format
885
+ 16 . __Export lists__: we use `fourmolu ` to automatically format export
886
+ lists. See the [`fourmolu . yaml` config][fourmolu - config]. We format
887
887
export lists in the following way:
888
888
889
889
```haskell
@@ -917,7 +917,7 @@ the rules below, it is good practice to update the code's style to match them.
917
917
) where
918
918
```
919
919
920
- * Why :* this is consistent with how `stylish - haskell ` formats it when
920
+ * Why :* this is consistent with how `fourmolu ` formats it when
921
921
importing it.
922
922
923
923
When intentionally hiding the constructor of a datatype or newtype , we add
@@ -978,7 +978,7 @@ the rules below, it is good practice to update the code's style to match them.
978
978
18 . __Records__:
979
979
980
980
We purposefully discourage the use of `RecordWildCards `.
981
-
981
+
982
982
For records we often use `NamedFieldPuns ` to make it convenient to extract
983
983
fields from the record. We use the following convention when naming fields
984
984
to avoid duplicate record fields (we do not use `DuplicateRecordFields `):
@@ -1123,10 +1123,10 @@ the rules below, it is good practice to update the code's style to match them.
1123
1123
import Foo.C (fooC , ...)
1124
1124
1125
1125
```
1126
-
1126
+
1127
1127
* Why :* this leads to more changes to the export list, but makes it
1128
1128
absolutely clear where each identifier comes from.
1129
-
1129
+
1130
1130
## Guidelines
1131
1131
1132
1132
There are more general guidelines on how we write and structure code.
@@ -1204,4 +1204,4 @@ There are more general guidelines on how we write and structure code.
1204
1204
use that shared code in a test suite defined in another package. To avoid
1205
1205
this problem, we avoid sharing source directories in ` cabal ` files.
1206
1206
1207
- [ stylish -config] : https://github.com/IntersectMBO/ouroboros-consensus/blob/master/.stylish-haskell .yaml
1207
+ [ fourmolu -config] : https://github.com/IntersectMBO/ouroboros-consensus/blob/master/fourmolu .yaml
0 commit comments