Do you gain any operations when you constrain a generic type using where T : struct?

Question

This may be a bit of an abstract question, so apologies in advance.

I am looking into generics in .NET, and was wondering about the where T : struct constraint.

I understand that this allows you to restrict the type used to be a value type. My question is, without any type constraint, you can do a limited number of operations on T.

Do you gain the ability to use any additional operations when you specify where T : struct, or is the only value in restricting the types you can pass in?

Edit

Some interesting answers so far, thanks. I guess the question I am actually asking is that if i were to write, (in a discussion about how to use generics),

"Now that you have constrained the type argument to value types, you can also do _________ on/with objects of that type"

Is there anything to put in that blank? I can think of things for the other constraints, but not this one.

Answer 1

All that T : struct gains you is an implicit new() constructor, and a few obvious things involving null. Perhaps more importantly, callers can't use classes, interfaces or Nullable<T>.

What types of operations are you after? For operators, try dynamic in 4.0, or MiscUtil in 3.5

Answer 2

No, you don't gain any operations on T by specifying the where T: struct generic type constraint. You constrain your callers to only specify value types (except Nullable<T> value types, which are not allowed).

Answer 3

The only thing that you gain relative to other possible sets of constraints is the ability to work with values of type Nullable<T> (which is why T: struct prohibits caller from passing Nullable<T> as a type parameter - it can't be nested).