[Issue 2025] Inconsistent rules for instantiating templates with a tuple parameter

[d-bugmail at puremagic.com]

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



--- Comment #13 from yebblies <yebblies at gmail.com> 2012-02-02 01:51:55 EST ---
(In reply to comment #12)
> (In reply to comment #11)
> > No, MATCHconvert means 'match with implicit conversions'.  These are the same
> > match levels used for normal function argument matching.
> 
> int is a type.  T as a template parameter denotes exactly that - a type.  So
> what implicit conversion is being performed?

None.  That's why it's a hack to use it to represent deduced args with no spec
type.  That's why it causes problems...

If you really want to understand how dmd does template deduction and overload
matching have a poke around in template.c (deduceFunctionTemplateMatch and
matchArgs) and mtype.c (callMatch).

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