[m-dev.] for review: type specialization (relative) [1]

[Simon Taylor]

> 
> That new relative diff looks good.  So I'm basically pretty happy with this
> change now.
> 
> There's still two small issues regarding the documentation which I raised
> that you have not yet addressed or commented on:
> 
> 	- "I suggest s/small enough/simple enough/"
> 	- Is --user-guided-type-specialization enabled at -O2 or -O3?

Sorry, I forgot to include the diff for that file.
compiler/options.m was changed to enable
--user-guided-type-specialization at -O2.

--- reference_manual.texi	Thu Apr 22 14:42:57 1999
+++ /home/pgrad/stayl/mercury0/doc/reference_manual.texi	Wed Apr 21 11:15:45 1999
@@ -4638,11 +4638,11 @@
 unify or compare polymorphic variables is most effective when
 the specialized types are built-in types such as @samp{int}, @samp{float}
 and @samp{string}, or enumeration types, since their unification and
-comparison procedures are small and can be inlined.
+comparison procedures are simple and can be inlined.
 
 Predicates or functions which make use of type class method calls
 may also be candidates for specialization. Again, this is most effective
-when the called type class methods are small enough to be inlined.
+when the called type class methods are simple enough to be inlined.
 
 @node Implementation specific details
 @subsection Implementation specific details
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------