summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Lykah <lykahb@gmail.com>2021-05-26 16:17:59 -0600
committerMarge Bot <ben+marge-bot@smart-cactus.org>2021-05-28 15:32:01 -0400
commitf74204c4f6f3f386c9688ca45a893f68894ecacd (patch)
treea8a8dd174324aa5b1cd6486592004b6213c9b695
parent6de8ac892a8001d1a0f00c7b44a731f1f9f5c0b1 (diff)
downloadhaskell-f74204c4f6f3f386c9688ca45a893f68894ecacd.tar.gz
Document release when TypeApplications allowed declaring variables as inferred
-rw-r--r--docs/users_guide/exts/type_applications.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/users_guide/exts/type_applications.rst b/docs/users_guide/exts/type_applications.rst
index 08aeb8e9e5..a459e1966d 100644
--- a/docs/users_guide/exts/type_applications.rst
+++ b/docs/users_guide/exts/type_applications.rst
@@ -187,8 +187,9 @@ in type and class declarations are ordered (:ref:`inferring-variable-order`).
Manually defining inferred variables
------------------------------------
-While user-written type or kind variables are specified by default, GHC permits
-labelling these variables as inferred. By writing the type variable binder in
+Since the 9.0.1 release, GHC permits labelling the user-written
+type or kind variables as *inferred*, in contrast
+to the default of *specified*. By writing the type variable binder in
braces as ``{tyvar}`` or ``{tyvar :: kind}``, the new variable will be
classified as inferred, not specified. Doing so gives the programmer control
over which variables can be manually instantiated and which can't.