[Issue 7378] inout constructors do not properly resolve to immutable.

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sat Dec 7 22:16:30 PST 2013


https://d.puremagic.com/issues/show_bug.cgi?id=7378


Kenji Hara <k.hara.pg at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|regression                  |enhancement


--- Comment #4 from Kenji Hara <k.hara.pg at gmail.com> 2013-12-07 22:16:21 PST ---
(In reply to comment #3)
> This used to work for me and I agree with Steven.
> 
> I think the bug type should be changed to "regression". Hope this will be fixed
> in 2.064.

Don't mark this issue as a regression. Before my patch applied, qualified
constructor (including a constructor that is qualified with inout) had not been
defined properly. So _nothing_ used to work. Therefore, this is still an
enhancement.

Honestly, current inout constructor and unique constructor definition has a
serious type-system hole that is presented in the bug 11503. I'm planning
fixing the issues by redesigning the definitions of inout/unique constructor -
the base concept would be same as the base of DIP49.

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


More information about the Digitalmars-d-bugs mailing list