[commit: ghc] master: Small doc fix (06c2547)
git at git.haskell.org
git at git.haskell.org
Sat Jan 23 12:43:12 UTC 2016
Repository : ssh://git@git.haskell.org/ghc
On branch : master
Link : http://ghc.haskell.org/trac/ghc/changeset/06c2547326773db85af9c8a076d6ad2710aa5912/ghc
>---------------------------------------------------------------
commit 06c2547326773db85af9c8a076d6ad2710aa5912
Author: Adam Sandberg Eriksson <adam at sandbergericsson.se>
Date: Sat Jan 23 13:13:07 2016 +0100
Small doc fix
Reviewers: austin, bgamari
Reviewed By: bgamari
Subscribers: thomie
Differential Revision: https://phabricator.haskell.org/D1828
>---------------------------------------------------------------
06c2547326773db85af9c8a076d6ad2710aa5912
docs/users_guide/glasgow_exts.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index d4ca508..055a558 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -12623,7 +12623,7 @@ optionally had by adding ``!`` in front of a variable.
``Strict`` implies :ref:`StrictData <strict-data>`.
-- **Function definitions.**
+- **Function definitions**
When the user writes ::
@@ -12635,7 +12635,7 @@ optionally had by adding ``!`` in front of a variable.
Adding ``~`` in front of ``x`` gives the regular lazy behavior.
-- **Let/where bindings.**
+- **Let/where bindings**
When the user writes ::
@@ -12691,7 +12691,7 @@ optionally had by adding ``!`` in front of a variable.
all get implicit bangs on the ``x`` pattern.
-- ** Nested patterns **
+- **Nested patterns**
Notice that we do *not* put bangs on nested patterns. For
example ::
@@ -12710,7 +12710,7 @@ optionally had by adding ``!`` in front of a variable.
:ref:`strict-modularity` below). So ``p`` and ``q`` may end up bound to
undefined. See also :ref:`recursive-and-polymorphic-let-bindings` below.
-- **Top level bindings.**
+- **Top level bindings**
are unaffected by ``Strict``. For example: ::
@@ -12720,7 +12720,7 @@ optionally had by adding ``!`` in front of a variable.
Here ``x`` and the pattern binding ``(y,z)`` remain lazy. Reason:
there is no good moment to force them, until first use.
-- **Newtypes.**
+- **Newtypes**
There is no effect on newtypes, which simply rename existing types.
For example: ::
More information about the ghc-commits
mailing list