[m-users.] Why can't `det` be used where `multi` is expected.
Philip White
philipwhite at cedarville.edu
Tue Aug 6 12:15:54 AEST 2019
Quoting Philip White (2019-08-05 22:09:34)
> Quoting Julien Fischer (2019-08-05 21:10:20)
> >
> > On Mon, 5 Aug 2019, Philip White wrote:
> >
> > > Quoting Julian Fondren (2019-08-05 01:46:30)
> > >> On 2019-08-04 23:02, Philip White wrote:
> > >> mds.m:022: in argument 1 of call to predicate
> > >> `getopt.process_options'/4:
> > >> mds.m:022: mode error: variable `OptionOps' has instantiatedness
> > >> mds.m:022: unique(
> > >> mds.m:022: option_ops_multi(
> > >> mds.m:022: /* unique */ (pred(in, out) is semidet),
> > >> mds.m:022: /* unique */ (pred(in, out) is semidet),
> > >> mds.m:022: /* unique */ (pred(out, out) is det)
> > >> mds.m:022: )
> > >> mds.m:022: ),
> > >
> > > Wow, the formatting really helps a lot; I'll make sure to reformat
> > > errors in the future. Maybe I'm getting errors wrong, but for me,
> > > mds.err has both the expected and actual instantiatedness one the same
> > > one line (well, multiple lines due to line wrapping). Errors don't get
> > > logged by default for me, so I've been passing the -E flag.
> > >
> > > Is there a way to have errors get pretty-printed?
> >
> > They *should* be formatted by default; you'll have to provide us with a
> > bit more information.
> >
> > Julien.
>
> Below is my terminal session; and no, my email client didn't wrap the
> text. mmc is version 14.0.1 - OS is NixOS, which is a pretty nonstandard
> distribution, so maybe it has something to do with some weird patch. I
> can't think of anything that my dotfile would be doing to
> make these errors get reflowed.
>
> <shell session>
> ...
> <end shell session>
>
> Philip.
Just tried a more recent release-of-the-day and I got nicer formatting.
Philip.
More information about the users
mailing list