Summary: template class name unconsistent behavior
           Product: D
           Version: D2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DMD

--- Comment #0 from 2012-09-16 19:43:14 PDT ---
(from my previous post:

Is that a bug?

The code below returns:


if we uncomment "auto c=make!A(1.0);", we get:


module main;
import std.stdio;
class A(T){
    T x;
    this(T x){this.x=x;}
auto make(alias a,T...)(T args){
    return new a!T(args);
void main(){
    //auto c=make!A(1.0);
    auto b=new A!double(1.0);

If this behavior is not a bug, I wonder what's the rationale, but also, how can
we have such a "make" function that doesn't mess up the template class name
depending on the order of which is used first (the make!T variant or the new
A!T) ?

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

Reply via email to