[m-rev.] for review: automatically generate all type_ctor_infos on non C backends

Peter Ross pro at missioncriticalit.com
Sat Nov 22 01:23:57 AEDT 2003

On Fri, Nov 21, 2003 at 01:43:59PM +1100, Fergus Henderson wrote:
> If you really wanted to have an explicit definition for every type, I would
> suggest a new form of definition
> 	:- type int is builtin.
> but since that still wouldn't suffice for tuples and higher-order types,
> I don't think it is worth the effort.
I disagree, I think every type that can be declared should be and that
it should be provided with a user defined equality and comparison

If you look at the complexity of how the RTTI ended up being done on the
.NET backend for the builtin types versus the situation now (better but
far from perfect).  I think this situation would have been avoided if we
had tried to declare everything that we could and then added the code to
the compiler to interpret these structures and generate the appropiate
backend code.
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

More information about the reviews mailing list