[m-rev.] for review: functional dependencies (3/3)

[Ralph Becket]

Mark Brown, Wednesday, 20 April 2005:
> Index: doc/reference_manual.texi
> ===================================================================
> +the type variables appearing in the type signature of the method.
> +A variable is determined by a type signature if it appears in the
> +type signature, but if functional dependencies are present
> +then it may also be determined from other variables
> +(@pxref{Functional dependencies}).

I think s/from other variables/from the other variables/ is better.

> + at node Functional dependencies
> + at section Functional dependencies
> +
> +Type classes may be defined to have functional dependencies between arguments.
> +There may be any number of functional dependencies on one typeclass.
> +Each constraint is expressed with the same syntax as typeclass constraints
> +on typeclass declarations, using a special constraint of the form
> + at code{(@var{Domain} -> @var{Range})}.

I think this paragraph could be more clearly expressed as

	Type class constraints may include any number of functional
	dependencies.  A functional dependency constraint takes the
	form @code{(@var{Domain} -> @var{Range})}.

Otherwise that all looks great.

-- Ralph
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------