On Monday, 10 October 2016 at 09:03:53 UTC, Sönke Ludwig wrote:
Of course, the new error is more restrictive than it should be, namely if the uninitialized pointer field gets written before the first read, it would still be safe.
That's surprising b/c void initializers for struct fields didn't use to work. I need to research the intent behind this to say sth. detailed, though usually an shouldn't break working code, only deprecate it.
