[m-dev.] for review: allow impurity on class methods

[Fergus Henderson]

On 25-Mar-2000, David Glen JEFFERY <dgj at ender.cs.mu.oz.au> wrote:
> Allow class methods to be impure or semipure. Previously any purity annotation
> on a class method was ignored, and the method assumed to be pure. (We have
> for some time caught the case of providing an impure implementation for
> a (pure) class method, though).

That looks good.

I've only got a couple of comments:
	- it would probably be a good idea to mention
	  somewhere in the language reference manual
	  that you can have impure methods
	  (and that you can't have impure higher-order types)
	- it would be a good idea to include some
	  `semipure' methods in the test case

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------