--- Comment #3 from Kenji Hara <> 2011-07-22 07:50:59 PDT ---
(In reply to comment #2)
> I think it's best to leave things as they are and close this. Automatic
> expansion is a bad thing. Consider for example:
> struct Tuple(T...) {
>     T data;
>     alias data this;
> }
> void doStuff(Tuple!(uint, float) t) {}
> void doStuff(uint a, float b) {}
> In this case we need to introduce a new rule that says the tuple should NOT be
> expanded if there's a matching function, or a new rule that makes the call
> ambiguous.

This case does not introduce ambiguous. Alias this lookup will run only when
original type matching fails. So 1st doStuff will match.
We can treat tuple expansion on function arguments based on alias this rule,
not any new rule.

My patch also work like it.
func6_22 call with Tup!(int, string) object matches 2nd overload version.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to