[m-rev.] for review: fix mantis bug 354
zoltan.somogyi at runbox.com
Sat Aug 30 08:47:22 AEST 2014
On Fri, 29 Aug 2014 23:59:44 +1000 (EST), Julien Fischer <jfischer at opturion.com> wrote:
> > +:- type table_io_args_data
> > + ---> table_io_args_data(
> > + % The number of head variables are stored in the answer
> s/are/that are/
> > + value = (MR_Word) MR_make_string_const(
> > + "the arguments are not available due to the presence of one or more typeclass constraints");
> Are they "typeclass constraints" or "type class constraints"? The reference
> manual uses the latter. (The contents of the .err_exp files in tests/invalid
> are divided on the subject.)
I think both are correct, though we tend to use "typeclass constraints"
when differentiating them from other kinds of constraints.
I followed your suggestion here as well.
I am committing this binary incompatible change.
More information about the reviews