Constraints (F#)

Constraints (F#)

This topic describes constraints that you can apply to generic type parameters to specify the requirements for a type argument in a generic type or function.

type-parameter-list when constraint1 [ and constraint2]

There are several different constraints you can apply to limit the types that can be used in a generic type. The following table lists and describes these constraints.




Type Constraint

type-parameter :> type

The provided type must be equal to or derived from the type specified, or, if the type is an interface, the provided type must implement the interface.

Null Constraint

type-parameter : null

The provided type must support the null literal. This includes all .NET object types but not F# list, tuple, function, class, record, or union types.

Explicit Member Constraint

type-parameter [or ... or type-parameter] : member-signature

At least one of the type arguments provided must have a member that has the specified signature; not intended for common use.

Constructor Constraint

type-parameter : ( new : unit -> 'a )

The provided type must have a default constructor.

Value Type Constraint

: struct

The provided type must be a .NET value type.

Reference Type Constraint

: not struct

The provided type must be a .NET reference type.

Enumeration Type Constraint

: enum<underlying-type>

The provided type must be an enumerated type that has the specified underlying type; not intended for common use.

Delegate Constraint

: delegate<tuple-parameter-type, return-type>

The provided type must be a delegate type that has the specified arguments and return value; not intended for common use.

Comparison Constraint

: comparison

The provided type must support comparison.

Equality Constraint

: equality

The provided type must support equality.

Unmanaged Constraint

: unmanaged

The provided type must be an unmanaged type. Unmanaged types are either certain primitive types (sbyte, byte, char, nativeint, unativeint, float32, float, int16, uint16, int32, uint32, int64, uint64, or decimal), enumeration types, nativeptr<_>, or a non-generic structure whose fields are all unmanaged types.

You have to add a constraint when your code has to use a feature that is available on the constraint type but not on types in general. For example, if you use the type constraint to specify a class type, you can use any one of the methods of that class in the generic function or type.

Specifying constraints is sometimes required when writing type parameters explicitly, because without a constraint, the compiler has no way of verifying that the features that you are using will be available on any type that might be supplied at run time for the type parameter.

The most common constraints you use in F# code are type constraints that specify base classes or interfaces. The other constraints are either used by the F# library to implement certain functionality, such as the explicit member constraint, which is used to implement operator overloading for arithmetic operators, or are provided mainly because F# supports the complete set of constraints that is supported by the common language runtime.

During the type inference process, some constraints are inferred automatically by the compiler. For example, if you use the + operator in a function, the compiler infers an explicit member constraint on variable types that are used in the expression.

Community Additions

© 2015 Microsoft