[commit: ghc] master: Fix comment typos that interfere with syntax highlighting (e87d158)

git at git.haskell.org git at git.haskell.org
Fri Aug 30 16:16:10 CEST 2013


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

On branch  : master
Link       : http://ghc.haskell.org/trac/ghc/changeset/e87d158d1580d13a39dc926c3fc17b12c856285a/ghc

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

commit e87d158d1580d13a39dc926c3fc17b12c856285a
Author: Patrick Palka <patrick at parcs.ath.cx>
Date:   Thu Mar 21 10:40:16 2013 -0400

    Fix comment typos that interfere with syntax highlighting


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

e87d158d1580d13a39dc926c3fc17b12c856285a
 compiler/simplCore/OccurAnal.lhs   |    2 +-
 compiler/specialise/SpecConstr.lhs |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/compiler/simplCore/OccurAnal.lhs b/compiler/simplCore/OccurAnal.lhs
index 52c5645..75d5364 100644
--- a/compiler/simplCore/OccurAnal.lhs
+++ b/compiler/simplCore/OccurAnal.lhs
@@ -1643,7 +1643,7 @@ When the scrutinee is a GlobalId we must take care in two ways
  i) In order to *know* whether 'x' occurs free in the RHS, we need its
     occurrence info. BUT, we don't gather occurrence info for
     GlobalIds.  That's the reason for the (small) occ_gbl_scrut env in 
-    OccEnv is for: it says "gather occurrence info for these.
+    OccEnv is for: it says "gather occurrence info for these".
 
  ii) We must call localiseId on 'x' first, in case it's a GlobalId, or
      has an External Name. See, for example, SimplEnv Note [Global Ids in
diff --git a/compiler/specialise/SpecConstr.lhs b/compiler/specialise/SpecConstr.lhs
index a5df7d5..0518367 100644
--- a/compiler/specialise/SpecConstr.lhs
+++ b/compiler/specialise/SpecConstr.lhs
@@ -560,7 +560,7 @@ Note [NoSpecConstr]
 ~~~~~~~~~~~~~~~~~~~
 The ignoreDataCon stuff allows you to say
     {-# ANN type T NoSpecConstr #-}
-to mean "don't specialise on arguments of this type.  It was added
+to mean "don't specialise on arguments of this type".  It was added
 before we had ForceSpecConstr.  Lacking ForceSpecConstr we specialised
 regardless of size; and then we needed a way to turn that *off*.  Now
 that we have ForceSpecConstr, this NoSpecConstr is probably redundant.





More information about the ghc-commits mailing list