[m-rev.] for review: messages for highly ambiguous overloading

Peter Ross pro at missioncriticalit.com
Fri Apr 21 09:22:55 AEST 2006


On Wed, Apr 19, 2006 at 04:11:32PM +1000, Zoltan Somogyi wrote:
> For review by anyone.
> 
> Zoltan.
> 
> When the typechecker finds highly ambiguous overloading, print what symbols
> were overloaded, and where they occurred. Without this information, it is
> very hard to fix the error if the predicate body is at all large.
> 
> Fix some software engineering problems encountered during this process.
> Modify some predicates in error_util in order to simplify their typical usage.
> Change the type_ctor type to be not simply a sym_name - int pair but a type
> with its own identifying type constructor. Change several other types that
> were also sym_name - int pairs (mode_id, inst_id, item_name, module_qual.id
> and the related simple_call_id) to have their own function symbols too.
> 
This will help us enormously, will it be going on the release branch?
If not then we will not be using 0.13 because fixing these is painful at
the moment.
--------------------------------------------------------------------------
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