1. What is the purpose of Clean?
The purpose of Clean is to serve as a fast, non-strict, purely functional programming language that is easy to optimize. Clean is characterized by lazy evaluation, which means that only arguments that need to be evaluated in a function call are actually evaluated. In addition, Clean functions can be written to use (partially) strict evaluation when necessary. Unlike R6RS Scheme and similar to Haskell, Clean offers pattern-matching, guards, array comprehensions, and a Hindley-Milner style type inferencing scheme . For I/O-related functions, in contrast to Haskell's monads, Clean offers a uniqueness type inferencing system, which allows destructive transformation of state information within a purely functional framework. Clean is useful for writing relatively bug-free programs in fewer lines of code, and for formally proving properties of those programs, thereby often eliminating the need for debugging.
2. What are the advantages of Clean?
Clean has the following advantages over similar functional programming languages:
- Efficient running-time of compiled code: Clean is one of the fastest functional programming languages. For many applications, Clean is appreciably faster than Haskell, and at least on par with OCaml. According to a Gentoo benchmark, the current Clean entry runs the meteor-contest benchmark 2.6 times faster than the corresponding Haskell GHC entry.
- Easy optimization of code: According to at least one user on Stay Hungry, Stay Foolish - Blog, Clean code can be easier to optimize than Haskell code. Also, according to one user on Nabble - Haskell - Haskell-Cafe - Why can't Haskell be faster?, "[T]he Clean type system gives more information to the compiler than the Haskell system does. The Haskell type system doesn't say that a certain value can be updated in-place or that a certain value should not be boxed (not counting the GHC extension for unboxed types)." (quote by Reinier). In addition, according to another user there, "[C]lean's uniqueness types allow for a certain kind of zero-copy mutation optimisation which is much harder for a haskell compiler to automatically infer." (quote by Jules).
- For discussions on how Clean optimizes its code vs. Haskell, see the following:
3. Why do some users call the language "Concurrent Clean?"
According to Concurrent Clean - Wikibooks, collection of open-content textbooks, "'Concurrent' refers to Clean's ability to run the same process on several computers, similar to Ada."
Further, according to History of "Clean Functional Language.": msg#00030,
- We started the work on Clean in 1984, as part of the Parallel Reduction Machine project.
- In the beginning, Clean was meant as an intermediate language.
- The first version was defined and running in 1987.
- Hereafter Clean was turned into a fully featured functional programming language.
- Special features are its Graph Rewriting Semantics (1987, Barendregt, Plasmeijer, Van Eekelen) which is
- still the core semantics of Clean, Eric Nockers strictness analyser (1994, very recently completely
- formally proven to be correct), the uniqueness typing (Smetsers, Barendsen,Plasmeijer), the object I/O
- library (Peter Achten), the concurrent implementation (Marco Kesseler), and, of course the very good
- code generation (John van Groningen).
- There is many more.
- You can find all our papers on the net:
- We had a lot of influence on Haskell (which started in 1987) and later also
- Haskell influenced Clean.
Another reason is that the word "Clean," being a generic adjective, by itself, usually generates too many false positives in a search on the Interent. Users in other countries who do not speak English and who only know how to search by name would have a hard time in finding Clean if that were its only name. "Concurrent Clean," however, is much easier to find as a name on the Internet, and can be used even by users in other countries who do not speak English.