D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 5801 - Using typeof() in function header breaks ITFI and default template arguments.
Summary: Using typeof() in function header breaks ITFI and default template arguments.
Status: RESOLVED DUPLICATE of issue 4413
Alias: None
Product: D
Classification: Unclassified
Component: dmd (show other issues)
Version: D2
Hardware: Other Mac OS X
: P2 major
Assignee: No Owner
URL:
Keywords: rejects-valid
Depends on:
Blocks:
 
Reported: 2011-03-30 15:55 UTC by David Nadlinger
Modified: 2011-12-21 05:55 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description David Nadlinger 2011-03-30 15:55:34 UTC
The following program compiles (bar uses a default type for T, baz relies on IFTI):
---
void bar(T = double)(int i) {}
void baz(T)(int i, T t) {}
void main() {
    bar(2);
    baz(3, "baz");
}
---

But if typeof() is used instead of explicitly specifying int, neither calls to bar and baz work any longer:
---
int a;
void bar(T = double)(typeof(a) i) {}
void baz(T)(typeof(a) i, T t) {}
void main() {
    bar(2);  // Does not compile.
    baz(3, "baz"); // Does not compile.
}
---

The respective error messages are:
Error: template test.bar(T = double) does not match any function template declaration
Error: template test.bar(T = double) cannot deduce template function from argument types !()(int)
and
Error: template test.baz(T) does not match any function template declaration
Error: template test.baz(T) cannot deduce template function from argument types !()(int,string).

If the template parameter is specified explicitly, however, both of the examples work again:
---
int a;
void bar(T = double)(typeof(a) i) {}
void baz(T)(typeof(a) i, T t) {}
void main() {
    bar!double(2);
    baz!string(3, "baz");
}
---

DMD from Git master at b7133502.
Comment 1 bearophile_hugs 2011-03-30 16:31:00 UTC
Take a look at bug 4413 to see if this is a dupe.
Comment 2 David Nadlinger 2011-04-10 14:08:36 UTC
(In reply to comment #1)
> Take a look at bug 4413 to see if this is a dupe.

I'm not sure – it's certainly not a direct duplicate, but the root cause might be the same.
Comment 3 Kenji Hara 2011-12-21 05:55:25 UTC

*** This issue has been marked as a duplicate of issue 4413 ***