views:

739

answers:

3

Let me give example:

  1. I have some generic class/interface definition:

    interface IGenericCar< T > {...}

  2. I have another class/interface that I want to relate with class above, for example:

    interface IGarrage< TCar > : where TCar: IGenericCar< (any type here) > {...}

Basically, I want my generic IGarrage to be dependent on IGenericCar, regardless if it's IGenericCar<int> or IGenericCar<System.Color>, because I don't have any dependency to that type.

+1  A: 

Would it make any sense to do something like:

interface IGenericCar< T > {...}
interface IGarrage< TCar, TCarType > 
    where TCar: IGenericCar< TCarType > {...}
Snarfblam
+9  A: 

There are typically 2 ways to achieve this

Option1: Add another parameter to IGarrage represnting the T which should be passed into the IGenericCar<T> constraint

interface IGarrage<TCar,TOther> where TCar : IGenericCar<TOther> { ... }

Option2: Define a base interface for IGenericCar<T> which is not generic and constrain against that interface

interface IGenericCar { ... }
interface IGenericCar<T> : IGenericCar { ... }
interface IGarrage<TCar> where TCar : IGenericCar { ... }
JaredPar
+1 for `IGenericCar`
Adam Robinson
A: 

Hmm... yes.

Jared's example is closer to what I had in mind, and that's avoiding explicit type reference.

Idea was to avoid back-reference in generic constraint (because they don't work), so adding extra non-generic interface could be way around.

Thanks to all.

File