[mercury-users] io__error

Michael Day mikeday at yeslogic.com
Thu Aug 1 10:50:15 AEST 2002

> The rationale for this design is that it allows future Mercury
> implementations to provide more information about the kind of error,
> without needing to change the interface of procedures which return
> an io__res(T).

Then what about making io__error more public, or making it an instance of
a typeclass with an error_message function, so that the various result
types can be used in other situations, with other error types?


mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe

More information about the users mailing list