Re: [m-users.] IO argument clobbering

Volker Wysk <[email protected]> Mon, 17 Jul 2023 17:07:29 +0200

Newsgroups	gmane.comp.lang.mercury.general
Message-ID	<[email protected]>

Am Montag, dem 17.07.2023 um 15:52 +0100 schrieb Sean Charles
(emacstheviking):
> Zoltan, Volker...... yes!
> 
> That makes it compile and run just fine.... I am not sure I fully comprehend but I will go and RTFM some more, that might help.

"in" is an abbreviation for "in(ground)". "ground" means normal data,
nothing callable. A predicate isn't ground. Its inst is like you have
defined it in your ":- inst callback == ...".

Cheers,
Volker

> 
> Thank you both.
> 
> 
> > On 17 Jul 2023, at 15:37, Zoltan Somogyi <[email protected]> wrote:
> > 
> > 
> > On 2023-07-17 16:27 +02:00 CEST, "Sean Charles (emacstheviking)" <[email protected]> wrote:
> > > :- type callback == (pred(world, world, io, io)).
> > > :- inst callback == (pred(in, out, di, uo) is det).
> > > 
> > > :- pred run_loop(
> > >    callback::in, world::in, world::out, io::di, io::uo
> > > ) is det.
> > 
> > Without compileable example code I cannot be sure, but I think
> > the problem is the "callback::in" in the declaration of run_loop.
> > What happens when you replace it with "callback:in(callback)"?
> > The mode checker needs this to tell it the mode of the higher order arg.
> > 
> > Zoltan.
> 
> _______________________________________________
> users mailing list
> [email protected]
> https://lists.mercurylang.org/listinfo/users

_______________________________________________
users mailing list
[email protected]
https://lists.mercurylang.org/listinfo/users

signature.asc (application/pgp-signature, 833 B)