[commit: ghc] ghc-8.0: users_guide: Fix various issues (4aadd5f)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/ghc

On branch  : ghc-8.0
Link       : http://ghc.haskell.org/trac/ghc/changeset/4aadd5f9f1df1922a963fc14d5d335b9ba6d544f/ghc

>---------------------------------------------------------------

commit 4aadd5f9f1df1922a963fc14d5d335b9ba6d544f
Author: Ben Gamari <bgamari.foss at gmail.com>
Date:   Thu Mar 24 22:32:04 2016 +0100

    users_guide: Fix various issues
    
    Sphinx apparently expects references to anchors that don't accompany a
    header to have a caption.
    
    Test Plan: validate
    
    Reviewers: austin
    
    Subscribers: thomie
    
    Differential Revision: https://phabricator.haskell.org/D2033
    
    (cherry picked from commit 2cebbe657afd6a3c31dd1d2b7d04978525c27a56)


>---------------------------------------------------------------

4aadd5f9f1df1922a963fc14d5d335b9ba6d544f
 docs/users_guide/glasgow_exts.rst | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index c1cd56f..c05db45 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -1840,8 +1840,9 @@ The following syntax is stolen:
        single: Quasi-quotes
 
     Stolen by: :ghc-flag:`-XQuasiQuotes`. Moreover, this introduces an ambiguity
-    with list comprehension syntax. See
-    :ref:`quasi-quotes-list-comprehension-ambiguity` for details.
+    with list comprehension syntax. See the
+    :ref:`discussion on quasi-quoting <quasi-quotes-list-comprehension-ambiguity>`
+    for details.
 
 ``$(``, ``$$(``, ``$varid``, ``$$varid``
     .. index::
@@ -7614,10 +7615,10 @@ Pretty-printing in the presence of kind polymorphism
 With kind polymorphism, there is quite a bit going on behind the scenes that
 may be invisible to a Haskell programmer. GHC supports several flags that
 control how types are printed in error messages and at the GHCi prompt.
-See :ref:`pretty-printing-types` for the details. If you are using
-kind polymorphism and are confused as to why GHC is rejecting (or accepting)
-your program, we encourage you to turn on these flags, especially
-:ghc-flag:`-fprint-explicit-kinds`.
+See the :ref:`discussion of type pretty-printing options <pretty-printing-types>`
+for further details. If you are using kind polymorphism and are confused as to
+why GHC is rejecting (or accepting) your program, we encourage you to turn on
+these flags, especially :ghc-flag:`-fprint-explicit-kinds`.
 
 .. index::
    single: TYPE
@@ -8696,11 +8697,14 @@ Here are the details:
   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 delcaration. 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.