diff options
author | Gabor Greif <ggreif@gmail.com> | 2014-07-21 10:39:35 +0200 |
---|---|---|
committer | Gabor Greif <ggreif@gmail.com> | 2014-07-21 10:40:11 +0200 |
commit | 4dd7ae620d7b2edc5b03d6f5bd0985006e9448e3 (patch) | |
tree | 17ef7e8735fa1e719caae6ba0fb5cffa41408b37 | |
parent | d3277f4f02aa93aac2715894f56a894e9ad86501 (diff) | |
download | haskell-4dd7ae620d7b2edc5b03d6f5bd0985006e9448e3.tar.gz |
Typos in note
-rw-r--r-- | compiler/types/Coercion.lhs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/compiler/types/Coercion.lhs b/compiler/types/Coercion.lhs index 2f499b704b..38f38ed50b 100644 --- a/compiler/types/Coercion.lhs +++ b/compiler/types/Coercion.lhs @@ -1799,13 +1799,13 @@ Note [Computing a coercion kind and role] To compute a coercion's kind is straightforward: see coercionKind. But to compute a coercion's role, in the case for NthCo we need its kind as well. So if we have two separate functions (one for kinds -and one for roles) we can get exponentially bad behaviour, sinc each -NthCo node makes a seaprate call to coercionKind, which traverses the +and one for roles) we can get exponentially bad behaviour, since each +NthCo node makes a separate call to coercionKind, which traverses the sub-tree again. This was part of the problem in Trac #9233. Solution: compute both together; hence coercionKindRole. We keep a separate coercionKind function because it's a bit more efficient if -the kind is all you wan. +the kind is all you want. \begin{code} coercionType :: Coercion -> Type |