[Issue 7191] ctor/opAssign doesn't play nice with field initialization

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=7191


Andrej Mitrovic <andrej.mitrovich at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement


--- Comment #3 from Andrej Mitrovic <andrej.mitrovich at gmail.com> 2013-09-17 15:47:28 PDT ---
(In reply to comment #2)
> (In reply to comment #1)
> 
> > I'm not sure whether or not we want to support this. Should field
> > initialization allow implicit calls to a ctor of that field?
> 
> I am not sure, but I think the current behavour is acceptable. If you want a
> different behavour in Line you can add a ctor to it.

The OP code was an attempt at providing convenience functionality, but when I
think about this now almost 2 years later, this just complicates the API. This
is not a feature I desperately need.

I'm marking this an enhancement though.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------