[m-dev.] Rethink of impurity w.r.t. solver code in negated contexts

Ian MacLarty maclarty at cs.mu.OZ.AU
Wed Dec 7 01:15:22 AEDT 2005

On 6 Dec 2005, at 14:35, Mark Brown wrote:

> implicit impurity is explicit).  It also has the nice property that 
> even if
> there is an unsound negation in a program main/2 must still be pure, 
> so if
> the program misbehaves we can deduce that there must be a broken 
> promise
> somewhere.

At the moment main can be impure and the compiler will not complain.  I 
don't really see an issue with this, but I thought I'd just point that 


mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au

More information about the developers mailing list