dupdefbug.d:
================================
class A {
int attr;
}
class B : A {
int attr;
}
================================
$ dmd.exe -c dupdefbug.d
no error reported.
It should report B.attr is dup of A.attr.
Comment #1 by bugzilla — 2007-08-13T13:34:11Z
Why should it be an error? Fields are not accessed virtually, so there is no hijacking problem. The current behavior is as designed.
If you feel it should be changed, please start a thread in digitalmars.D and present the case.
Comment #2 by someanon — 2007-08-13T13:46:25Z
Posted to digitalmars.D:
I think 90% of the time this happens it is a bug, not by the programmer's
intention.
If it's designed to be so in D, I propose to change it; or at least reported
by the compiler.