Function Selection when Using Parameterized Types (Generics)

[David Douglass]

I'm confused about the program below. Based on my reading of the C# spec, I
don't think it should compile, but it does when using Beta 1. Could somebody
please explain the function selection rules to me?

Thanks,
--
David Douglass
MCSD for Microsoft .NET
=============== =============== =============== ======
#region Using directives

using System;
using System.Collecti ons.Generic;
using System.Text;

#endregion

namespace CSharpSamples {
class FunctionOverloa ds {
static void Main(string[] args) {
FunctionOverloa ds1<ClassA> x = new FunctionOverloa ds1<ClassA>();
ClassA A = new ClassA();
x.Function1(A);
Console.ReadLin e();
}
public class ClassA {
}
public class FunctionOverloa ds1<typeParam> {

public void Function1(typeP aram arg) {
Console.WriteLi ne("Function1(t ypeParam arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'");
}
public void Function1(Class A arg) {
Console.WriteLi ne("Function1(C lassA arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'");
}

}
}
}

[Nick Malik]

care to share your confusion? I don't see what you are seeing that is
"wrong" with the code. What is it that you expect shouldn't compile?

--- Nick

"David Douglass" <Da***********@ discussions.mic rosoft.com> wrote in message
news:0D******** *************** ***********@mic rosoft.com...

I'm confused about the program below. Based on my reading of the C# spec, I don't think it should compile, but it does when using Beta 1. Could somebody please explain the function selection rules to me?

Thanks,
--
David Douglass
MCSD for Microsoft .NET
=============== =============== =============== ======
#region Using directives

using System;
using System.Collecti ons.Generic;
using System.Text;

#endregion

namespace CSharpSamples {
class FunctionOverloa ds {
static void Main(string[] args) {
FunctionOverloa ds1<ClassA> x = new FunctionOverloa ds1<ClassA>();
ClassA A = new ClassA();
x.Function1(A);
Console.ReadLin e();
}
public class ClassA {
}
public class FunctionOverloa ds1<typeParam> {

public void Function1(typeP aram arg) {
Console.WriteLi ne("Function1(t ypeParam arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'");
}
public void Function1(Class A arg) {
Console.WriteLi ne("Function1(C lassA arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'");
}

}
}
}

[David Douglass]

The program as written calls the function that takes ClassA as an argument.
But why not call the other signature that takes the type parameter? If the
function that takes ClassA as an argument is commented out, the other
function is called. Based on my reading of 20.1.8 of the C# Language
Specification, this seems ambiguous. Isn't this the same as F1 example in
20.1.8?

Thanks,
Dave

"Nick Malik" wrote:

care to share your confusion? I don't see what you are seeing that is
"wrong" with the code. What is it that you expect shouldn't compile?

--- Nick

"David Douglass" <Da***********@ discussions.mic rosoft.com> wrote in message
news:0D******** *************** ***********@mic rosoft.com...

I'm confused about the program below. Based on my reading of the C# spec,

I

don't think it should compile, but it does when using Beta 1. Could

somebody

please explain the function selection rules to me?

Thanks,
--
David Douglass
MCSD for Microsoft .NET
=============== =============== =============== ======
#region Using directives

using System;
using System.Collecti ons.Generic;
using System.Text;

#endregion

namespace CSharpSamples {
class FunctionOverloa ds {
static void Main(string[] args) {
FunctionOverloa ds1<ClassA> x = new FunctionOverloa ds1<ClassA>();
ClassA A = new ClassA();
x.Function1(A);
Console.ReadLin e();
}
public class ClassA {
}
public class FunctionOverloa ds1<typeParam> {

public void Function1(typeP aram arg) {
Console.WriteLi ne("Function1(t ypeParam arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'");
}
public void Function1(Class A arg) {
Console.WriteLi ne("Function1(C lassA arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'");
}

}
}
}

[Nick Malik]

Good catch Dave. I believe that you are correct. The code below should
throw a compiler error... According to the spec, it should not compile.

The good thing is that it calls the correct method. The method defined as
"Function1(type Param arg)" should not be called as long as the other one is
defined with the same method signature. As you demonstrated, it is never
called as long as the other one is defined and the parameter type is of the
same type.

To be honest, there is power in the way that this is defined. It allows the
author of the generic definition to place a "type-specific" implementation
of "Function1" into the class, and allow a "catch-all" method to handle any
new or unexpected types. It is also, in all liklihood, encouraging sloppy
coding practices. Powerful but sloppy. That's a compelling combination,
huh?

If anyone has any further insight, I join Dave in asking that you chime in.

--- Nick

"David Douglass" <Da***********@ discussions.mic rosoft.com> wrote in message
news:95******** *************** ***********@mic rosoft.com...

The program as written calls the function that takes ClassA as an argument. But why not call the other signature that takes the type parameter? If the function that takes ClassA as an argument is commented out, the other
function is called. Based on my reading of 20.1.8 of the C# Language
Specification, this seems ambiguous. Isn't this the same as F1 example in
20.1.8?

Thanks,
Dave

"Nick Malik" wrote:

care to share your confusion? I don't see what you are seeing that is
"wrong" with the code. What is it that you expect shouldn't compile?

--- Nick

"David Douglass" <Da***********@ discussions.mic rosoft.com> wrote in message news:0D******** *************** ***********@mic rosoft.com...

I'm confused about the program below. Based on my reading of the C# spec,

I

don't think it should compile, but it does when using Beta 1. Could

somebody

please explain the function selection rules to me?

Thanks,
--
David Douglass
MCSD for Microsoft .NET
=============== =============== =============== ======
#region Using directives

using System;
using System.Collecti ons.Generic;
using System.Text;

#endregion

namespace CSharpSamples {
class FunctionOverloa ds {
static void Main(string[] args) {
FunctionOverloa ds1<ClassA> x = new FunctionOverloa ds1<ClassA>();
ClassA A = new ClassA();
x.Function1(A);
Console.ReadLin e();
}
public class ClassA {
}
public class FunctionOverloa ds1<typeParam> {

public void Function1(typeP aram arg) {
Console.WriteLi ne("Function1(t ypeParam arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() +

"'"); }
public void Function1(Class A arg) {
Console.WriteLi ne("Function1(C lassA arg)");
Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'"); }

}
}
}

[David Douglass]

I can't really accept this. Developing a language like C# isn't a corporate
IT project where you make it up as you go along. I'm going to consider this
a bug in beta 1 and submit it to Microsoft. At a minimum it's a bug in the
spec.

Can anybody from Microsoft chime in on this?

Dave

"Nick Malik" wrote:

Good catch Dave. I believe that you are correct. The code below should
throw a compiler error... According to the spec, it should not compile.

The good thing is that it calls the correct method. The method defined as
"Function1(type Param arg)" should not be called as long as the other one is
defined with the same method signature. As you demonstrated, it is never
called as long as the other one is defined and the parameter type is of the
same type.

To be honest, there is power in the way that this is defined. It allows the
author of the generic definition to place a "type-specific" implementation
of "Function1" into the class, and allow a "catch-all" method to handle any
new or unexpected types. It is also, in all liklihood, encouraging sloppy
coding practices. Powerful but sloppy. That's a compelling combination,
huh?

If anyone has any further insight, I join Dave in asking that you chime in.

--- Nick

"David Douglass" <Da***********@ discussions.mic rosoft.com> wrote in message
news:95******** *************** ***********@mic rosoft.com...

The program as written calls the function that takes ClassA as an

argument.

But why not call the other signature that takes the type parameter? If

the

function that takes ClassA as an argument is commented out, the other
function is called. Based on my reading of 20.1.8 of the C# Language
Specification, this seems ambiguous. Isn't this the same as F1 example in
20.1.8?

Thanks,
Dave

"Nick Malik" wrote:

care to share your confusion? I don't see what you are seeing that is
"wrong" with the code. What is it that you expect shouldn't compile?

--- Nick

"David Douglass" <Da***********@ discussions.mic rosoft.com> wrote in message news:0D******** *************** ***********@mic rosoft.com...
> I'm confused about the program below. Based on my reading of the C# spec, I
> don't think it should compile, but it does when using Beta 1. Could
somebody
> please explain the function selection rules to me?
>
> Thanks,
> --
> David Douglass
> MCSD for Microsoft .NET
> =============== =============== =============== ======
> #region Using directives
>
> using System;
> using System.Collecti ons.Generic;
> using System.Text;
>
> #endregion
>
> namespace CSharpSamples {
> class FunctionOverloa ds {
> static void Main(string[] args) {
> FunctionOverloa ds1<ClassA> x = new FunctionOverloa ds1<ClassA>();
> ClassA A = new ClassA();
> x.Function1(A);
> Console.ReadLin e();
> }
> public class ClassA {
> }
> public class FunctionOverloa ds1<typeParam> {
>
> public void Function1(typeP aram arg) {
> Console.WriteLi ne("Function1(t ypeParam arg)");
> Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'"); > }
>
>
> public void Function1(Class A arg) {
> Console.WriteLi ne("Function1(C lassA arg)");
> Console.WriteLi ne("arg.GetType () = '" + arg.GetType().T oString() + "'"); > }
>
> }
> }
> }
>
>