If I have a generic interface with a struct constraint like this:
public interface IStruct where T : struct { }
I can
This issue is strange (arguably), but expected, behavior.
The class System.Enum itself could be supplied as the type of T. Being a class, System.Enum is of course not a struct!
public class MCVE<T> where T : Enum { }
public class MCVE2 : MCVE<Enum> { }
As explained by contributor HaloFour:
This is an odd behavior by the CLR itself.
System.Enumis a class, but every type that derives fromSystem.Enumis astruct. So a constraint onSystem.Enumby itself doesn't implystructsince you could passSystem.Enumas the generic type argument...It is weird, but it was easier to simply remove the imposed limitation on the compiler than to argue over different syntax for "enum" constraints that might have different behavior.
The solution is to make it your standard practice to constrain to struct, Enum when you wish to constrain concrete types to being any specific enumeration. If additionally you wish to accept the class System.Enum as your generic type, only then would you constrain to Enum.