Error about @disabled constructor when there is a custom one
Dmitry Olshansky
dmitry.olsh at gmail.com
Tue Jan 22 13:12:45 PST 2013
23-Jan-2013 00:28, Minas Mina пишет:
> From Jonathan M Davis:
>
> "...At this point, I don't think that the situation with default
> constructors and
> structs is going to change. It's a result of requiring init properties
> for all
> types, and is thus a "forced fault" in the language..."
>
> Why does requiring init properties for all types results in this? What
> does that even mean?
I don't buy it either. 0-argument constructor have nothing to do with
requiring .init.
--
Dmitry Olshansky
More information about the Digitalmars-d
mailing list