Since some computer scientists use category theory, I was wondering if there are any programming languages that use it extensively.
Haskell is a purely functional language. However side-effects are (almost by definition) difficult to incorporate into a functional language. This is an important problem since I/O is a very important side-effect for most computer programs. Haskell's method of incorporating side-effects is to use monads.
One of the simplest ways to get a monad is from a pair of adjoint functors.
For more on monads see:
(1) Embûches tissues blog: Monads in Mathematics 1: examples
(2) A series of lectures on youtube by TheCatsters:
Pairs of adjoint functors are fairly common and I've found they provide a useful way for seeing part of the "big-picture" in many different branches of mathematics.
Here is one of several introductions to pairs of adjoint functors from the Concrete Nonsense blog.
All of the answers so far are based on Cartesian closed categories. There are a few languages based on Cartesian categories, which reject use of higher-order functions in the base language:
- The key example are Joseph Goguen's OBJ languages for programming with algebras, based on order-sorted Cartesian categories. Goguen's rejection of higher-order functions is explained in his Higher-order functions considered unnecessary for higher-order programming.
- The programming language Maude, based on rewriting logic, is probably the fittest successor of OBJ. Cf. Goguen's OBJ Family page, which summarises the programming languages in this family.
- The mathematical payoff to rejecting the "closed" part of Cartesian closed categories is that this opens the possibility of easier modelling of colimit constructions; I'd love to see a good reference for this point, one that explores that practical difficulties higher-order functions cause, but the general issue is easy enough to see. This has been important for approaches to programming languages that are based on various pushout constructions for specifying rewrites. Cf. Gibbons (2002) Towards a colimit-based semantics for visual programming.
I'd say every statically typed functional language is such. Why? There's a well-known relation between propositions and types, or more precisely between certain theories of logic and certain type theories going by the name of Curry--Howard correspondence. This relation has a less well-known cousin known as Curry--Howard--Lambek correspondence that extends it to categories. Thus, because every reasonable statically typed functional language is based on type theory, it has direct connection to category theory as well. You simply cannot escape it, try as you might. Bob Harper likes to call this The Holy Trinity -- categories, languages and logic.
The list of such languages follows: Haskell, ML, OCaml, Idris, Coq, Agda, etc.
Of course, you have to take all of this with a grain of salt. Safe for Coq and Agda -- both of which are foremost theorem provers -- these languages contain many industry-driven quirks that make them less susceptible to the formal reasoning mentioned in the first paragraph.
In a bit different direction, because type theory is so expressive (for example, it can replace set theory as foundations of mathematics), it's fairly straightforward to express many algebraic structures in it. All of the above languages use this feature profoundly, with e.g. monads in Haskell playing a very prominent role.
Here's (internet archive link) another one based on Hagino's thesis, asides charity. Implemented both in Haskell and Ruby.
CAML by definition is Categorical Abstract Machine Language,
however I am not cetain that you can say that an language explicitly uses category theory. Perhaps you are asking "Are there languages that allow Category Theory Concepts to be easily represented?" or perhaps you are asking if the compilation or interpretation of a particular programming language uses Category Theory in its implementation?
While technically, all Turing-complete capable languages should be equivalently able to express the same set of computations, some languages do so more elegantly than others, allowing the programmer or mathematician to be more eloquent.
I would say LISP and SCHEME, even though based on lambda-calculus, are more connected to the spirit of category theory in concept. While the numbers and integers are conceptually defined as atomic and can be built up from primitives in concept and in theory; in practice, the implementations of SCHEME and LISP and (CLU) tend to take shortcuts to speed up implementation.
The hierarchical ability to pass functions and functions of functions (etc.) as first-class parameters to functions in LISP and SCHEME let you be able to emulate the actions or morphisms of category theory better in that language than others. You just have to start from the ground up, as I have not yet seen a library or package in LISP or SCHEME for category theory.
"The notion of categorical abstract machine, or CAM arose in the mid-1980s and in computer science takes a place of a kind of theory of computation for programmers. In a theory CAM is represented by Cartesian closed category (c.c.c.) and embedded into the combinatory logic."
Caml (aka the basis for Microsoft's F#) is an acronym for Categorical Abstract Machine Language.
Other interesting reading is A Categorical Manifesto by Joseph Goguen.
His language project is the OBJ family of languages.
The U.S. government has sponsored reseach in using category theory-based languages (e.g. https://www.kestrel.edu/home/projects/) with the hope specifying systems as the composition of theories using category theory to combine and refine these theories into executable robust code. The language used on some of the projects listed at the link above use the specification language Metaslang which has a subset which is executable. One side effect of this reseach led to our supporting the development of CRYPTOL, a good example of specifying a domain specific language using the functional language Haskell. In my use of Metaslang and the development environment (emacs/Specware), it is difficult to get "normal" programmers to use algebraic specification and functional programming. Despite being some of the nicest people I have met, Haskell programmers are definitely NOT normal. (;-)
Also see here.