From e65c60d9d12d3f63f7e35108c77fd45aaf384603 Mon Sep 17 00:00:00 2001 From: qrczak Date: Fri, 19 Oct 2001 22:16:28 +0000 Subject: [PATCH] [project @ 2001-10-19 22:16:28 by qrczak] Typo. --- ghc/docs/comm/the-beast/vars.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ghc/docs/comm/the-beast/vars.html b/ghc/docs/comm/the-beast/vars.html index 55d11ee..a3060bf 100644 --- a/ghc/docs/comm/the-beast/vars.html +++ b/ghc/docs/comm/the-beast/vars.html @@ -78,7 +78,7 @@ data VarDetails The TyVar case is self-explanatory. The MutTyVar case is used only during type checking. Then a -tupe variable can be unified, using an imperative update, with a type, +type variable can be unified, using an imperative update, with a type, and that is what the IORef is for. The Bool field records whether the type variable arose from a type signature, in which case it should not be unified with a type (only with another -- 1.7.10.4