summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorsheaf <sam.derbyshire@gmail.com>2022-07-21 13:19:27 +0200
committerMarge Bot <ben+marge-bot@smart-cactus.org>2022-07-28 13:57:38 -0400
commitfc23b5ed0f7924308040bf4163fc0a6da176feed (patch)
tree93bde6d457db51cd4dbac71b747e19758a34f225
parentef30e21594e44af309c627052f63aea6fd575c9e (diff)
downloadhaskell-fc23b5ed0f7924308040bf4163fc0a6da176feed.tar.gz
Docs: fix mistaken claim about kind signatures
This patch fixes #21806 by rectifying an incorrect claim about the usage of kind variables in the header of a data declaration with a standalone kind signature. It also adds some clarifications about the number of parameters expected in GADT declarations and in type family declarations.
-rw-r--r--docs/users_guide/exts/poly_kinds.rst45
1 files changed, 37 insertions, 8 deletions
diff --git a/docs/users_guide/exts/poly_kinds.rst b/docs/users_guide/exts/poly_kinds.rst
index ad10e1b188..5eef04dbd2 100644
--- a/docs/users_guide/exts/poly_kinds.rst
+++ b/docs/users_guide/exts/poly_kinds.rst
@@ -472,7 +472,7 @@ Standalone kind signatures and declaration headers
--------------------------------------------------
GHC requires that in the presence of a standalone kind signature, data
-declarations must bind all their inputs. For example: ::
+declarations must bind all their parameters For example: ::
type Prox1 :: k -> Type
data Prox1 a = MkProx1
@@ -485,7 +485,7 @@ declarations must bind all their inputs. For example: ::
-- • In the data type declaration for ‘Prox2’
-GADT-style data declarations may either bind their inputs or use an inline
+GADT-style data declarations may either bind their parameters or use an inline
signature in addition to the standalone kind signature: ::
type GProx1 :: k -> Type
@@ -502,9 +502,19 @@ signature in addition to the standalone kind signature: ::
data GProx3 :: k -> Type where MkGProx3 :: GProx3 a
-- OK.
- type GProx4 :: k -> Type
- data GProx4 :: w where MkGProx4 :: GProx4 a
- -- OK, w ~ (k -> Type)
+ type GProx4 :: k1 -> Type
+ data GProx4 :: k2 -> Type where MkGProx4 :: GProx4 a
+ -- OK.
+
+Note that variables in a kind signature must stand for variables, not
+arbitrary types. For example, the following is rejected: ::
+
+ type GProx5 :: k -> Type
+ data GProx5 :: w where MkGProx5 :: GProx5 a
+ -- Error:
+ -- • Couldn't match expected kind ‘w’ with actual kind ‘k -> Type’
+ -- • In the data type declaration for ‘GProx5’
+
Classes are subject to the same rules: ::
@@ -519,10 +529,29 @@ Classes are subject to the same rules: ::
-- with actual kind ‘Type -> Constraint’
-- • In the class declaration for ‘C2’
-On the other hand, type families are exempt from this rule: ::
+For type families, the number of parameters in the kind signature takes on
+additional meaning: it specifies the arity of the type family, i.e. how many
+arguments the type family requires before reducing.
+Any type family instances must then provide the same number of arguments.
+For example: ::
+
+ type F1 :: Type -> Type
+ type family F1 where
+ F1 = Maybe
+ -- OK.
+
+ type F2 :: Type -> Type
+ type family F2 where
+ F2 () = Bool
+ F2 a = Maybe a
+ -- Error:
+ -- • Number of parameters must match family declaration; expected 0
+ -- • In the type family declaration for `F2'
- type F :: Type -> Type
- type family F
+ type F3 :: Type -> Type
+ type family F3 a where
+ F3 () = Bool
+ F3 a = Maybe a
-- OK.
Data families are tricky territory. Their headers are exempt from this rule,