[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2018-05-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

Manu  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #13 from Manu  ---
I can no longer reproduce this.

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-07-22 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

Marco Leise  changed:

   What|Removed |Added

 CC||marco.le...@gmx.de

--- Comment #12 from Marco Leise  ---
Hmm, recently I see different "overlapping fields" error messages popping up
after certain types of deprecations are detected on the involved fields. There
may be a connection: https://issues.dlang.org/show_bug.cgi?id=16312

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-06-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #11 from joeyemm...@yahoo.com ---
(In reply to Steven Schveighoffer from comment #10)
> (In reply to joeyemmons from comment #9)
> > Created attachment 1601 [details]
> > Shows Issue 15498
> > 
> > The error seems to be printed for no reason at all except to confuse
> > things...
> 
> 
> Hm.. definitely the error is confusing, but the code itself has another
> error (hwCursorRef is not defined).
> 
> Do you have a reproduction that doesn't involve another error?

No, I only seem to get this error to print when in the presence of other
errors, but as far as I can tell this error should not be printing and only
confuses things. 

Really annoying when it pops up and really has nothing to do with the actual
problem... very unhelpful...

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-06-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #10 from Steven Schveighoffer  ---
(In reply to joeyemmons from comment #9)
> Created attachment 1601 [details]
> Shows Issue 15498
> 
> The error seems to be printed for no reason at all except to confuse
> things...


Hm.. definitely the error is confusing, but the code itself has another error
(hwCursorRef is not defined).

Do you have a reproduction that doesn't involve another error?

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-06-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #9 from joeyemm...@yahoo.com ---
Created attachment 1601
  --> https://issues.dlang.org/attachment.cgi?id=1601&action=edit
Shows Issue 15498

The error seems to be printed for no reason at all except to confuse things...

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-06-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

joeyemm...@yahoo.com changed:

   What|Removed |Added

 CC||joeyemm...@yahoo.com

--- Comment #8 from joeyemm...@yahoo.com ---
I am getting this too, definitely don't have any unions. My issue seems to be
caused by some kind of import ordering problem, reordering some of my imports
makes it go away. Making a minimized reproduction might be hard.

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #7 from Kenji Hara  ---
(In reply to Steven Schveighoffer from comment #6)
> Is there any way to define ComponentInfo or SharedString such that info and
> baseClass overlap? I wouldn't think so.

I don't know. So this is funny issue. I'm waiting more information from Manu.

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #6 from Steven Schveighoffer  ---
(In reply to Kenji Hara from comment #5)
> If there's no unions (overlapped fields), the error print would be a
> compiler bug.
> 
> Honestly I cannot say anything until I see what the "some stuff" actually is.

I would also like to see what is in there, but even without that, the error
report is at least misleading.

Note the error once again:

Error: struct libep.componentdesc.ComponentDesc destructors, postblits and
invariants are not allowed in overlapping fields info and baseClass

And the struct ComponentDesc:

struct ComponentDesc
{
  ComponentInfo info;
  SharedString baseClass;
}

Is there any way to define ComponentInfo or SharedString such that info and
baseClass overlap? I wouldn't think so.

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #5 from Kenji Hara  ---
(In reply to Steven Schveighoffer from comment #4)
> But what about if there are no unions? Manu says no unions are being used.
> 
> In his code, there is no unions where the error is being printed (info
> conflicts with baseClass).

If there's no unions (overlapped fields), the error print would be a compiler
bug.

Honestly I cannot say anything until I see what the "some stuff" actually is.

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #4 from Steven Schveighoffer  ---
(In reply to Kenji Hara from comment #3)
> Minimized example code that compiler shows the error message.

But what about if there are no unions? Manu says no unions are being used.

In his code, there is no unions where the error is being printed (info
conflicts with baseClass).

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #3 from Kenji Hara  ---
Minimized example code that compiler shows the error message.

struct X
{
this(this) {}
// or: ~this() {}
// or: invariant {}
}

union U // Error
{
X x;
int overlapping;
}

struct S // Error
{
union
{
X x;
int overlapping;
}
}

For U or S, compiler cannot generate destructors, postblits, or invariants
automatically, because the field x typed X overlapping with other fields.

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

Steven Schveighoffer  changed:

   What|Removed |Added

 CC||schvei...@yahoo.com

--- Comment #2 from Steven Schveighoffer  ---
the /+ some stuff +/ might be the cause. I don't see any postblits, invariants,
etc. anywhere either.

Can you elaborate there? Maybe a minimal reproduction?

--


[Issue 15498] Unhelpful error message "destructors, postblits and invariants are not allowed in overlapping fields"

2016-03-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15498

--- Comment #1 from Manu  ---
I'm still stuck on this... what does the error mean?

--