From ce3a3edbbe688b3a284d3c5508fade0eb2ff532f Mon Sep 17 00:00:00 2001
From: simonmar <unknown>
Date: Tue, 13 Aug 2002 10:13:40 +0000
Subject: [PATCH] [project @ 2002-08-13 10:13:40 by simonmar] Update docs
 about not using Float.

---
 ghc/docs/users_guide/sooner.sgml |    9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/ghc/docs/users_guide/sooner.sgml b/ghc/docs/users_guide/sooner.sgml
index 474b5a3..767de16 100644
--- a/ghc/docs/users_guide/sooner.sgml
+++ b/ghc/docs/users_guide/sooner.sgml
@@ -464,14 +464,15 @@ to compete with it, but link with it.
 </Para>
 </ListItem>
 </VarListEntry>
+
 <VarListEntry>
 <Term>Don't use <Literal>Float</Literal>s:</Term>
 <ListItem>
 <Para>
-We don't provide specialisations of Prelude functions for <Literal>Float</Literal>
-(but we do for <Literal>Double</Literal>).  If you end up executing overloaded
-code, you will lose on performance, perhaps badly.
-</Para>
+If you're using <literal>Complex</literal>, definitely use
+<literal>Complex Double</literal> rather than <literal>Complex
+Float</literal> (the former is specialised heavily, but the latter
+isn't).</para>
 
 <Para>
 <Literal>Floats</Literal> (probably 32-bits) are almost always a bad idea, anyway,
-- 
1.7.10.4