Possible Duplicate:
Solution for overloaded operator constraint in .NET generics
I have a problem I’m working on, currently it is working for int
s but i want it to work for all classes that can be added using the +
operator. Is there any way to define this in the generic? For example,
public List<T> Foo<T>() where T : ISummable
Is there any way to do this?
EDIT:
Performance of passing in a delegate to do the summing instead of using += with a type of Int was 540% slower at best. Investigating possible other solution
Final solution:
Thank you all for your suggestions. I ended up with a solution which is not too slow and enforces the checking at compile time. I cannot take full credit as a colleague helped me arrive at this. Anyway, here it is:
Implement an interface with all of the required operators on it in the form of functions
public interface IFoo<InputType, OutputType>
{
//Adds A to B and returns a value of type OutputType
OutputType Add(InputType a, InputType b);
//Subtracts A from B and returns a value of type OutputType
OutputType Subtract(InputType a, InputType b);
}
Create the class you want to define, but instead of the Where clause, use a dependency injected instance of the IFoo interface. the OutputType will most often be double because the nature of the operations is mathematical.
public class Bar<T>
{
private readonly IFoo<T,double> _operators;
public Bar(IFoo<T, double> operators)
{
_operators = operators;
}
}
now when you use this class, you define the rules for operation like this:
private class Foo : IFoo<int, double>
{
public double Add(int a, int b)
{
return (double)(a+b);
}
public double Subtract(int a, int b)
{
return (double)(a-b);
}
}
then you would use it like this:
Foo inttoDoubleOperations = new Foo();
Bar myClass = new Bar(Foo);
that way all the operations are enforced at compile time :)
enjoy!
dynamic
, and it’s the least useful workaround for the problem at hand. – Tempietempla