... | @@ -267,7 +267,7 @@ It's possible that you might experience some typechecker errors due to this chan |
... | @@ -267,7 +267,7 @@ It's possible that you might experience some typechecker errors due to this chan |
|
|
|
|
|
- The `DataD`, `NewtypeD`, `DataInstD`, and `NewtypeInstD` constructors now take a `[DerivCxtQ]` instead of a `CxtQ` to represent `deriving` clauses ([\#10598](https://gitlab.haskell.org//ghc/ghc/issues/10598)). This change was necessary because:
|
|
- The `DataD`, `NewtypeD`, `DataInstD`, and `NewtypeInstD` constructors now take a `[DerivCxtQ]` instead of a `CxtQ` to represent `deriving` clauses ([\#10598](https://gitlab.haskell.org//ghc/ghc/issues/10598)). This change was necessary because:
|
|
|
|
|
|
- Due to the introduction of [deriving strategies](https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/DerivingStrategies), data types can now accept multiple deriving clauses (hence the need for `[DerivCxtQ]` instead of `DerivCxtQ`).
|
|
- Due to the introduction of [deriving strategies](https://gitlab.haskell.org/trac/ghc/wiki/Commentary/Compiler/DerivingStrategies), data types can now accept multiple deriving clauses (hence the need for `[DerivCxtQ]` instead of `DerivCxtQ`).
|
|
- Each deriving clause now allows an optional strategy keyword, so a new `DerivClause` data type was introduced that contains a `Maybe DerivStrategy` in addition to the usual `Cxt`.
|
|
- Each deriving clause now allows an optional strategy keyword, so a new `DerivClause` data type was introduced that contains a `Maybe DerivStrategy` in addition to the usual `Cxt`.
|
|
|
|
|
|
>
|
|
>
|
... | | ... | |