Perhaps a context ID would be useful?  Could even encode it into the message ID...

LOL. I use message IDs in the C++ compiler. I like using the text ones...

On Tue, 11 Jul 2006 15:53:11 +1000, Walter Bright <newshound@digitalmars.com> wrote...

I like to keep error messages generated by different parts of the compiler slightly different...

...an alias and the other is a typedef.  I suppose it could be debated which...

Yes, that is a bug.

Generally, the compiler tries to invent a fix to continue...

...a different error message.

-------------------------------

module test1;

typedef foo bar;
typedef bar foo;

void main () {
        foo...

...Do? Do?? Do?!  ;)  Why not 'default'?  Or 'typedef'?  (Actually, that'd be cute.)

I still...

...return to the typedef issue for a moment, if you do:

    typedef char* pchar;

    template...

...TypeInfo_Typedef object downcasted to TypeInfo.

Checking the base at runtime:
#
# assert( is(x == typedef...