[commit: ghc] master: Delete obsolete docs on GADT interacton with TypeApplications (2be55b8)
git at git.haskell.org
git at git.haskell.org
Fri Oct 13 13:13:59 UTC 2017
Repository : ssh://git@git.haskell.org/ghc
On branch : master
Link : http://ghc.haskell.org/trac/ghc/changeset/2be55b85b4c7479639b01c3b8f47c1e49ddbcb0a/ghc
>---------------------------------------------------------------
commit 2be55b85b4c7479639b01c3b8f47c1e49ddbcb0a
Author: Ryan Scott <ryan.gl.scott at gmail.com>
Date: Fri Oct 13 09:10:21 2017 -0400
Delete obsolete docs on GADT interacton with TypeApplications
Even since ef26182e2014b0a2a029ae466a4b121bf235e4e4, this section of
the users' guide is wrong, as there are no longer special rules for
the order of type variables in GADT constructors' type signatures
vis-à-vis visible type application. As a result, this section can
simply be deleted, as there is no longer anything interesting to say
about the topic.
>---------------------------------------------------------------
2be55b85b4c7479639b01c3b8f47c1e49ddbcb0a
docs/users_guide/glasgow_exts.rst | 16 ----------------
1 file changed, 16 deletions(-)
diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index 9402885..9e16ebd 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -10125,22 +10125,6 @@ Here are the details:
if you want the most accurate information with respect to visible type
application properties.
-- Data constructors declared with GADT syntax follow different rules
- for the time being; it is expected that these will be brought in line
- with other declarations in the future. The rules for GADT
- data constructors are as follows:
-
- * All kind and type variables are considered specified and available for
- visible type application.
-
- * Universal variables always come first, in precisely the order they
- appear in the type declaration. Universal variables that are
- constrained by a GADT return type are not included in the data constructor.
-
- * Existential variables come next. Their order is determined by a user-
- written `forall`; or, if there is none, by taking the left-to-right order
- in the data constructor's type and doing a stable topological sort.
-
.. _implicit-parameters:
Implicit parameters
More information about the ghc-commits
mailing list