[Issue 5500] Appender.put causes an invariant violation in struct with overloaded opAssign
https://issues.dlang.org/show_bug.cgi?id=5500 Justin Whear jus...@economicmodeling.com changed: What|Removed |Added Status|NEW |RESOLVED CC||jus...@economicmodeling.com Resolution|--- |WORKSFORME --- Comment #7 from Justin Whear jus...@economicmodeling.com --- Cannot repro in 2.065. Closing as WORKSFORME. --
[Issue 5500] Appender.put causes an invariant violation in struct with overloaded opAssign
http://d.puremagic.com/issues/show_bug.cgi?id=5500 Jameson beatgam...@gmail.com changed: What|Removed |Added CC||beatgam...@gmail.com --- Comment #6 from Jameson beatgam...@gmail.com 2013-05-23 00:05:43 PDT --- I can't reproduce this: DMD 2.062 LDC2 (based on 2.061) Arch Linux x86_64 Can anyone else reproduce this? This bug is quite old... -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5500] Appender.put causes an invariant violation in struct with overloaded opAssign
http://d.puremagic.com/issues/show_bug.cgi?id=5500 --- Comment #4 from Jonathan M Davis jmdavisp...@gmx.com 2011-01-31 17:40:56 PST --- Actually, I think I know what's happening (roughly speaking). This problem is caused by bug# 5058. Appender has uninitialized data which it then tries to assign to using the assignment operator. Because the invariant is called before opAssign (which I argue in bug# 5058, that it shouldn't be), the invariant is called on garbage data. Sometimes, that garbage data violates the invariant, and sometimes it doesn't. So, unless there's something that Appender can do to work around bug# 5058, it's likely not a bug in Appender so much as it's a bug in how invariants work with regards to opAssign. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5500] Appender.put causes an invariant violation in struct with overloaded opAssign
http://d.puremagic.com/issues/show_bug.cgi?id=5500 --- Comment #5 from Nicolas Sicard dran...@free.fr 2011-01-31 22:50:35 PST --- Actually, I think I know what's happening (roughly speaking). This problem is caused by bug# 5058. I think you are right, these bugs look very similar. It definitely is related to opAssign, since it never occurs when opAssign is not redefined. This would also mean that the compiler-generated opAssign is either not calling invariant() or calling it at the right time, after data is properly initialized. But I don't know what happens behind the scene in this matter. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
