[Issue 4028] delegates with differing default arguments lead to same template instantiation

[d-bugmail at puremagic.com]

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


Don <clugdbug at yahoo.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clugdbug at yahoo.com.au


--- Comment #8 from Don <clugdbug at yahoo.com.au> 2011-04-06 07:10:00 PDT ---
(In reply to comment #7)
> Is it possible/good to encode the simple constant default arguments (ints,
> strings, etc) in the type/signature of the delegate, and refuse the other types
> of default arguments?

What good would adding that corner case be?
I think it's just a bizarre and silly feature. It's a horrendously complicated
and confusing way of doing one special case of currying.
If you really need this ability (which I doubt), you can achieve the same thing
via a struct with two opCall overloads.

Just kill it.

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