https://issues.dlang.org/show_bug.cgi?id=15847
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from [email protected] --- "It simply isn't possible to detect that the variable is void-initialized in the general case." While it could be done reasonably well with flow control analysis, I agree that it's a lot of work for a small return. Thus it makes more sense to disallow void initialization for types with a custom opAssign. "But note that void-initialization is already @system..." Okay, I forgot this point, and it does mitigate my concerns. I will close this bug. --
