[commit: ghc] ghc-8.2: Typos in bang patterns user manual [skip ci] (d4fa088)

git at git.haskell.org git at git.haskell.org
Mon Apr 10 23:30:52 UTC 2017


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

On branch  : ghc-8.2
Link       : http://ghc.haskell.org/trac/ghc/changeset/d4fa088350913233520ffa7163ef188a63666262/ghc

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

commit d4fa088350913233520ffa7163ef188a63666262
Author: Ömer Sinan Ağacan <omeragacan at gmail.com>
Date:   Mon Apr 10 18:38:31 2017 +0300

    Typos in bang patterns user manual [skip ci]
    
    (cherry picked from commit b1acb167b93f62eefab3f8cb24518eb0ce410d8c)


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

d4fa088350913233520ffa7163ef188a63666262
 docs/users_guide/glasgow_exts.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index 89b970c..cf8bb43 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -12007,7 +12007,7 @@ Replace the "Translation" there with the following one.  Given
     Replace any binding ``p = e``, where ``p`` is not a variable, with
     ``v = e; x1 = case v of p -> x1; ...; xn = case v of p -> xn``, where
     ``v`` is fresh and ``x1``.. ``xn`` are the bound variables of ``p``.
-    Again if ``e`` is a variable, you can optimised his by not introducing a
+    Again if ``e`` is a variable, this can be optimised by not introducing a
     fresh variable.
 
 The result will be a (possibly) recursive set of bindings, binding
@@ -12017,7 +12017,7 @@ non-recursive using ``fix``, but we do not do so in Core, and it only
 obfuscates matters, so we do not do so here.)
 
 The translation is carefully crafted to make bang patterns meaningful
-for reursive and polymorphic bindings as well as straightforward
+for recursive and polymorphic bindings as well as straightforward
 non-recursive bindings.
 
 Here are some examples of how this translation works. The first



More information about the ghc-commits mailing list