[Issue 5931] keyword new won't allow default initialization of a struct where it has a non-zero argument constructor

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

[Issue 5931] keyword new won't allow default initialization of a struct where it has a non-zero argument constructor

2011-05-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5931 Christopher the Magnificent ultimatemacfana...@gmail.com changed: What|Removed |Added Summary|keyword new insists on

[Issue 5931] keyword new won't allow default initialization of a struct where it has a non-zero argument constructor

2011-05-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5931 --- Comment #4 from kenn...@gmail.com 2011-05-06 12:47:28 PDT --- (In reply to comment #3) *Shouldn't* post-blit be invokable by calling File(file)? Wouldn't this be a desirable behavior? Sorry, got distracted by the 'this.file = new

[Issue 5931] keyword new won't allow default initialization of a struct where it has a non-zero argument constructor

2011-05-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5931 --- Comment #5 from kenn...@gmail.com 2011-05-06 12:48:43 PDT --- (In reply to comment #4) (In reply to comment #3) [snip] At the line above marked DOESN'T WORK, the compiler refuses to allocate a new default-initialized File struct.