Uniqueness of methods and limitations

Question

I came to the following:

public void AddConfig<T>(Config c)  where T : BaseTypeA
{
// do stuff
}

public void AddConfig<T>(Config c)  where T : BaseTypeB
{
// do stuff
}

I would love to do that. But I think this is not possible. The compiler ignores the restrictions. What for? (I know this by design).

I think my 2 options are:

• Make two different functions.
• Create 2 different configuration classes.

Right?

Answer 1

If you mean in the same class, then you are right (I do not think that the compiler checks that BaseTypeA and BaseTypeB cannot be converted to each other, that you will need to check to make sure that they are unique methods, i.e. e. something like where T : BaseTypeA && T !: BaseTypeBif you understand what I mean).

Having said that, why don't you do something like this:

 interface IConfigurable
 {
      void AddConfig(Config c)
 }

 public class BaseTypeA : IConfigurable

 public class BaseTypeB : IConfigurable

Answer 2

. .

, , , .