Hey guys!
First I'm not entirely sure if this goes into this forum, never the less.
I'm wondering why not allow code as the following:
public I MyFunc<I>(I param)
where I : Interface1
{
}
public I MyFunc<I>(I param)
where I: Interface2
{
}
As far as I can see this would work exactly as function overloading with the arguments:
public void MyFunc(Interface1 param)
{
}
public void MyFunc(Interface2 param)
{
}
This seems to be a matter of the compiler, as it doesn't seem to be impossible to incorporate into a future version of the compiler. Similar to how java does it.
generic parameter overloading
Hot Topic
- How to know Is Serializable?
- What does the ? mean in C#
- toolStrip and splitContainer problem
- Safe handle closed (?)
- Delete Entire Contents of Folder?
- Socket
- OLE Problem - An invalid VARIANT was detected during a conversion from an unmanaged VARIANT to a managed object
- What is the maximum literal address for a local file?
- DataTable.Select (string) problem
- System.Timers.Timer Exception Number must be either non-negative or -1. Parameter name: dueTime
generic parameter overloading
sofakng
public interface Interface1<RealT> {}
public interface Interface2<RealT> {}
public static I MyFunc<I>(Interface1<I> param)
where I: Interface1<I>
{
}
public static I MyFunc<I>(Interface2<I> param)
where I: Interface2<I>
{
}
Though it gets ugly real fast :S
Alvin Kuiper
Hi, bilsa
In this situation,
Imagine that if one instance of a class which implement Interface1 as well as Interface2 has been past to MyFunc, which should be choosed How can we decide to call the previous one or the other one
So, it is vague syntax. For this reason compiler surely cant allow this thing to happen.
In this way, the syntax is right, because you emplicitly show the interface name (Interface1 param or Interface2 param).
So, your calling MyFunc((Interface1)obj) is different from MyFunc((Interface2)obj).
Hope it is clear.
If you have further questions, pls feel free to let me know.
Thank you
vkan
Yes this is a limitation of the current implementation of the generics. They have a few other limitations too, btw. You should report this in connect: http://connect.microsoft.com/VisualStudio - Report it as a request for a future version. I have posted there a few things about generics too.
There are a few things that are possible in the CLR but not accessible from different languages. You could for example (in the CLR) overload a method by specifying a different return type. That is, for example, not supported by the C# compiler, although the runtime would support it.