[Issue 3680] default struct constructor should not be removed

2018-05-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3680 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 3680] default struct constructor should not be removed

2015-06-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3680 Andrei Alexandrescu and...@erdani.com changed: What|Removed |Added Version|unspecified |D2 --

[Issue 3680] default struct constructor should not be removed

2010-01-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3680 --- Comment #8 from Michel Nolard michel.nol...@gmail.com 2010-01-19 02:50:53 PST --- * This comment is more a remainder for myself than a new comment. * There is a way to introduce a opAssign( typeof( this ) rhs ) using templates, although

[Issue 3680] default struct constructor should not be removed

2010-01-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3680 Don clugd...@yahoo.com.au changed: What|Removed |Added CC||clugd...@yahoo.com.au

[Issue 3680] default struct constructor should not be removed

2010-01-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3680 --- Comment #4 from Michel Nolard michel.nol...@gmail.com 2010-01-15 03:13:06 PST --- Ok. I clearly see your point now, and it is both practical and logical ... and I agree ! This would be quite an improvement for a lot of situations. What

[Issue 3680] default struct constructor should not be removed

2010-01-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3680 --- Comment #5 from ibrahim YANIKLAR yanik...@gmail.com 2010-01-15 08:43:21 PST --- What bothers me is this : To remove static opCall's completely is another subject... I will explain that by opening a new issue. A case which needs

[Issue 3680] default struct constructor should not be removed

2010-01-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3680 --- Comment #6 from ibrahim YANIKLAR yanik...@gmail.com 2010-01-15 09:57:39 PST --- Also this(int a = 0) and static ... opCall(int a = 0) should be prohibited. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email

[Issue 3680] default struct constructor should not be removed

2010-01-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3680 --- Comment #7 from Don clugd...@yahoo.com.au 2010-01-15 11:45:32 PST --- (In reply to comment #6) Also this(int a = 0) and static ... opCall(int a = 0) should be prohibited. That's bug 3438. I think the underlying issue is, that we need