While sclv answered your direct question, I’ll add as an aside that there’s more than one possible meaning for “type-level lambda”. Haskell has a variety of type operators but none really behave as proper lambdas:
- Type constructors: Abstract type operators that introduce new types. Given a type
Aand a type constructor
F, the function application
F Ais also a type but carries no further (type level) information than “this is
- Polymorphic types: A type like
a -> b -> aimplicitly means
forall a b. a -> b -> a. The
forallbinds the type variables within its scope, thus behaving somewhat like a lambda. If memory serves me this is roughly the “capital lambda” in System F.
- Type synonyms: A limited form of type operators that must be fully applied, and can produce only base types and type constructors.
- Type classes: Essentially functions from types/type constructors to values, with the ability to inspect the type argument (i.e., by pattern matching on type constructors in roughly the same way that regular functions pattern match on data constructors) and serving to define a membership predicate on types. These behave more like a regular function in some ways, but are very limited: type classes aren’t first-class entities that can be manipulated, and they operate on types only as input (not output) and values only as output (definitely not input).
- Functional dependencies: Along with some other extensions, these allow type classes to implicitly produce types as results as well, which can then be used as the parameters to other type classes. Still very limited, e.g. by being unable to take other type classes as arguments.
- Type families: An alternate approach to what functional dependencies do; they allow functions on types to be defined in a manner that looks much closer to regular value-level functions. The usual restrictions still apply, however.
Other extensions relax some of the restrictions mentioned, or provide partial workarounds (see also: Oleg’s type hackery). However, pretty much the one thing you can’t do anywhere in any way is exactly what you were asking about, namely introduce new a binding scope with an anonymous function abstraction.