[m-dev.] for discussion: higher-order `any' insts
Julien Fischer
juliensf at csse.unimelb.edu.au
Mon Jan 14 13:59:35 AEDT 2008
On Wed, 9 Jan 2008, Mark Brown wrote:
> Programming with solver types and higher-order code in Mercury is a bit
> painful at the moment, because we have no way of safely handling pred and
> func expressions that may bind non-local solver variables. The current
> solution is to make such higher-order values impure (which, unfortunately,
> tends to then spread everywhere).
>
> The code below implements an alternative approach. This is designed to
> allow us to use solver types and higher-order code without resorting to
> impurity.
>
> Feedback is welcome (and happy new year, everyone :-))
The proposed new insts (and the implementation) look fine.
I have a couple of reservations about the change to the reference
manual, but I'm happy for you to commit as is (I need to think about it
a bit.)
You should add an entry to the NEWS file for the new feature as well.
Julien.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions: mercury-developers-request at csse.unimelb.edu.au
--------------------------------------------------------------------------
More information about the developers
mailing list