[m-rev.] for review: Fix abstract equivalence types.
Mark Brown
mark at mercurylang.org
Wed Aug 23 16:51:32 AEST 2017
Hi Dirk,
On Wed, Aug 23, 2017 at 4:27 PM, Dirk Ziegemeyer <dirk at ziegemeyer.de> wrote:
> What ist the reason for not using
> :- type var(T) == int.
> instead?
>
> I suppose that the compiler won’t recognise if we accidentally mix up two types which are both equivalent to int.
That's a good answer to your own question ;-)
>
> Would „:- type var(T) == int.“ have advantages over the current definition? E.g. regarding memory consumption or unification speed.
For an answer to this question, you could substitute "intentionally"
for "accidentally".
Mark
More information about the reviews
mailing list