[m-rev.] for post-commit review: optimize dummy types

[Julien Fischer]

On Wed, 5 Oct 2005, Zoltan Somogyi wrote:

> For post-commit review by anyone. I am committing this before review because
> the diff is so large that most other checkins can cause conflicts, which
> require rerunning bootchecks. The log message follows. The diff is in
> ~zs/tmp/DIFF.dummy; most of it is switches to four space indentation.
> Only the files with substantive comments in the log message below
> could really benefit from review.
>
> Zoltan.
>
> Consider types of the form
>
> 	:- type x ---> f.
>
> to be dummy types, since they contain no information. Optimize them the same
> way we currently optimize io.state and store.store.
>

Does this have any effect on type specialisation if one of the types
being specialised is a dummy type?  Could the the set_tree234 type
now just be defined as :- type set_tree234(T) == tree234(T, unit)
or is this definition still going to be less efficient than the
existing one in the library.

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