static opCall 'hidden' by incompatible constructors

[Nick Treleaven via Digitalmars-d]

On 17/07/2014 18:56, Dicebot wrote:
> It has never worked properly (opCall never got called) and being a bad
> style going against language design rationale it was completely banned.
> More info: https://issues.dlang.org/show_bug.cgi?id=12124

Thanks for the link. We need a note in the changelog about that IMO.

> I believe CTFE-only default struct constructors should be allowed

I'll just point out that I don't want *default* struct constructors, I 
understand the T.init issue. I want nullary constructor syntax that is 
called explicitly with brackets.

> instead but until this becomes an option, having factory functions is
> the way to go ("auto var = unique(new T)" vs "Unique!T var = new T")

OK.