Repository : ssh://darcs.haskell.org//srv/darcs/ghc On branch : master
http://hackage.haskell.org/trac/ghc/changeset/78ee29370e3eec7f8209e2a227a634428f1be4f1 >--------------------------------------------------------------- commit 78ee29370e3eec7f8209e2a227a634428f1be4f1 Author: David Terei <[email protected]> Date: Tue Nov 15 14:02:31 2011 -0800 Fix mistake in user guide >--------------------------------------------------------------- docs/users_guide/glasgow_exts.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml index 1eb041b..8026c85 100755 --- a/docs/users_guide/glasgow_exts.xml +++ b/docs/users_guide/glasgow_exts.xml @@ -8346,8 +8346,8 @@ happen. <para>A <literal>SPECIALIZE</literal> pragma for a function can be put anywhere its type signature could be put. Moreover, you can also <literal>SPECIALIZE</literal> an <emphasis>imported</emphasis> - provided it was given an <literal>INLINABLE</literal> pragma at its definition site - (<xref linkend="inlinable-pragma"/>)</para> + function provided it was given an <literal>INLINABLE</literal> pragma at + its definition site (<xref linkend="inlinable-pragma"/>).</para> <para>A <literal>SPECIALIZE</literal> has the effect of generating (a) a specialised version of the function and (b) a rewrite rule _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
