From: Dawid Toton <d0@wp.pl>
To: caml-list@inria.fr
Subject: [Caml-list] Re: Numbered modules in error messages
Date: Tue, 12 Jun 2012 16:40:33 +0200 [thread overview]
Message-ID: <4FD754E1.5000102@wp.pl> (raw)
In-Reply-To: <90B44972-C96B-435E-9353-5CF4F845FEBF@math.nagoya-u.ac.jp>
On 06/06/2012 06:23 PM, Jacques Garrigue wrote:
> On 2012/06/06, at 19:04, Dawid Toton wrote:
>
>>
>> I'm asking this, because from time to time I deal with error messages like "type abc is not compatible with abc" with both abc being exactly the same strings. I'm wondering whether it is possible to force the compiler to say something more, to explain the difference between these types.
>
> The output of numbers is triggered when the same identifier appears
> twice for different entities.
> So you should never have just "abc is not compatible with abc", as
> the internal unique identifiers should be printed also.
>
> Jacques Garrigue
I have checked that indeed I get these messages without the unique stamps mostly on the computer where the installed compiler is old.
Still it seems that identifiers are not always made unique, e.g. I just got the following message with 3.12.1:
Error: In this `with' constraint, the new definition of decor
does not match its original definition in the constrained signature:
Type declarations do not match:
type decor = Decor.t
is not included in
type decor = Decor.t
In this particular case the stamps would be not useful anyway.
But in general it would be nice if the Ident.stamp values could be translated to some corresponding locations in the source code.
For example Typecore.enter_variable could feed the available loc to Ident.create?
Dawid Toton
prev parent reply other threads:[~2012-06-12 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 10:04 [Caml-list] " Dawid Toton
2012-06-06 16:23 ` Jacques Garrigue
2012-06-12 14:40 ` Dawid Toton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD754E1.5000102@wp.pl \
--to=d0@wp.pl \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox