| Clojure | |
| Logo Size: | 120px |
| Paradigm: | multi-paradigm |
| Family: | Lisp |
| Designer: | Rich Hickey |
| Latest Release Version: | 1.11.2 |
| Memory Management: | Garbage collection via a host (JVM, CLR, a JavaScript runtime such as V8 in case of ClojureScript or BEAM (see below) |
| Dialects: | ClojureScript, ClojureDart |
| License: | Eclipse Public |
| Wikibooks: | Clojure Programming |
Clojure (like closure)[1] [2] is a dynamic and functional dialect of the Lisp programming language on the Java platform.[3] [4]
Like most other Lisps, Clojure's syntax is built on S-expressions that are first parsed into data structures by a reader before being compiled.[5] [1] Clojure's reader supports literal syntax for maps, sets and vectors along with lists, and these are compiled to the mentioned structures directly.[5] Clojure treats code as data and has a Lisp macro system.[6] Clojure is a Lisp-1 and is not intended to be code-compatible with other dialects of Lisp, since it uses its own set of data structures incompatible with other Lisps.[6]
Clojure advocates immutability and immutable data structures and encourages programmers to be explicit about managing identity and its states.[7] This focus on programming with immutable values and explicit progression-of-time constructs is intended to facilitate developing more robust, especially concurrent, programs that are simple and fast.[8] [9] [1] While its type system is entirely dynamic, recent efforts have also sought the implementation of a dependent type system.[10]
The language was created by Rich Hickey in the mid-2000s, originally for the Java platform; the language has since been ported to other platforms, such as the Common Language Runtime (.NET). Hickey continues to lead development of the language as its benevolent dictator for life.
Rich Hickey is the creator of the Clojure language.[3] Before Clojure, he developed dotLisp, a similar project based on the .NET platform,[11] and three earlier attempts to provide interoperability between Lisp and Java: a Java foreign language interface for Common Lisp (jfli),[12] A Foreign Object Interface for Lisp (FOIL),[13] and a Lisp-friendly interface to Java Servlets (Lisplets).[14]
Hickey spent about two and a half years working on Clojure before releasing it publicly in October 2007,[15] much of that time working exclusively on Clojure with no outside funding. At the end of this time, Hickey sent an email announcing the language to some friends in the Common Lisp community.
Clojure's name, according to Hickey, is a word play on the programming concept "closure" incorporating the letters C, L, and J for C#, Lisp, and Java respectively—three languages which had a major influence on Clojure's design.[2]
Rich Hickey developed Clojure because he wanted a modern Lisp for functional programming, symbiotic with the established Java platform, and designed for concurrency.[8] [9] [16] [1] He has also stressed the importance of simplicity in programming language design and software architecture, advocating for loose coupling, polymorphism via protocols and type classes instead of inheritance, stateless functions that are namespaced instead of methods or replacing syntax with data.[17] [18] [19]
Clojure's approach to state is characterized by the concept of identities,[7] which are represented as a series of immutable states over time. Since states are immutable values, any number of workers can operate on them in parallel, and concurrency becomes a question of managing changes from one state to another. For this purpose, Clojure provides several mutable reference types, each having well-defined semantics for the transition between states.[7]
Clojure runs on the Java platform and as a result, integrates with Java and fully supports calling Java code from Clojure,[20] [1] and Clojure code can be called from Java, too.[21] The community uses tools such as Clojure command-line interface (CLI) or Leiningen for project automation, providing support for Maven integration. These tools handle project package management and dependencies and are configured using Clojure syntax.
As a Lisp dialect, Clojure supports functions as first-class objects, a read–eval–print loop (REPL), and a macro system. Clojure's Lisp macro system is very similar to that of Common Lisp with the exception that Clojure's version of the backquote (termed "syntax quote") qualifies symbols with their namespace. This helps prevent unintended name capture, as binding to namespace-qualified names is forbidden. It is possible to force a capturing macro expansion, but it must be done explicitly. Clojure does not allow user-defined reader macros, but the reader supports a more constrained form of syntactic extension.[22] Clojure supports multimethods[23] and for interface-like abstractions has a protocol[24] based polymorphism and data type system using records,[25] providing high-performance and dynamic polymorphism designed to avoid the expression problem.
Clojure has support for lazy sequences and encourages the principle of immutability and persistent data structures. As a functional language, emphasis is placed on recursion and higher-order functions instead of side-effect-based looping. Automatic tail call optimization is not supported as the JVM does not support it natively;[26] [27] [28] it is possible to do so explicitly by using the recur keyword.[29] For parallel and concurrent programming Clojure provides software transactional memory,[30] a reactive agent system, and channel-based concurrent programming.[31]
Clojure 1.7 introduced reader conditionals by allowing the embedding of Clojure, ClojureScript and ClojureCLR code in the same namespace.[5] Transducers were added as a method for composing transformations. Transducers enable higher-order functions such as map and fold to generalize over any source of input data. While traditionally these functions operate on sequences, transducers allow them to work on channels and let the user define their own models for transduction.[32] [33] [34]
Extensible Data Notation, or edn,[35] is a subset of the Clojure language intended as a data transfer format. It can be used to serialize and deserialize Clojure data structures, and Clojure itself uses a superset of edn to represent programs.
edn is used in a similar way to JSON or XML, but has a relatively large list of built-in elements, shown here with examples:
true, false"foo bar"\c, \tabname:key1233.14(a b 42)[a b 42]{:a 1, "foo" :bar, [1 2 3] four}#{a b [1 2 3]}nil (a null-like value)In addition to those elements, it supports extensibility through the use of tags, which consist of the character # followed by a symbol. When encountering a tag, the reader passes the value of the next element to the corresponding handler, which returns a data value. For example, this could be a tagged element: #myapp/Person {:first "Fred" :last "Mertz"}, whose interpretation will depend on the appropriate handler of the reader.
This definition of extension elements in terms of the others avoids relying on either convention or context to convey elements not included in the base set.
The primary platform of Clojure is Java,[4] [20] but other target implementations exist. The most notable of these is ClojureScript,[36] which compiles to ECMAScript 3,[37] and ClojureCLR,[38] a full port on the .NET platform, interoperable with its ecosystem.
Other implementations of Clojure on different platforms include:
Tooling for Clojure development has seen significant improvement over the years. The following is a list of some popular IDEs and text editors with plug-ins that add support for programming in Clojure:[50]
In addition to the tools provided by the community, the official Clojure command-line interface (CLI) tools[63] have also become available on Linux, macOS, and Windows since Clojure 1.9.[64]
The development process is restricted to the Clojure core team, though issues are publicly visible at the Clojure JIRA project page.[65] Anyone can ask questions or submit issues and ideas at ask.clojure.org.[66] If it's determined that a new issue warrants a JIRA ticket, a core team member will triage it and add it. JIRA issues are processed by a team of screeners and finally approved by Rich Hickey.[67] [68]
With continued interest in functional programming, Clojure's adoption by software developers using the Java platform has continued to increase. The language has also been recommended by software developers such as Brian Goetz,[69] [70] [71] Eric Evans,[72] [73] James Gosling,[74] Paul Graham,[75] and Robert C. Martin.[76] [77] [78] [79] ThoughtWorks, while assessing functional programming languages for their Technology Radar,[80] described Clojure as "a simple, elegant implementation of Lisp on the JVM" in 2010 and promoted its status to "ADOPT" in 2012.[81]
In the "JVM Ecosystem Report 2018" (which was claimed to be "the largest survey ever of Java developers"), that was prepared in collaboration by Snyk and Java Magazine, ranked Clojure as the 2nd most used programming language on the JVM for "main applications".[82] Clojure is used in industry by firms[83] such as Apple,[84] [85] Atlassian,[86] Funding Circle,[87] Netflix,[88] Nubank,[89] Puppet,[90] and Walmart[91] as well as government agencies such as NASA.[92] It has also been used for creative computing, including visual art, music, games, and poetry.[93]
In the 2023 edition of Stack Overflow Developer Survey, Clojure was the fourth most admired in the category of programming and scripting languages, with 68.51% of the respondents who have worked with it last year saying they would like to continue using it. In the desired category, however it was marked as such by only 2.2% of the surveyed, whereas the highest scoring JavaScript was desired by 40.15% of the developers participating in the survey.[94] It could possibly be attributed to limited professional opportunities for Clojure developers with just over 50 search results for "Clojure developer" at the U.S. section of Indeed, as of May 2024.[95]
| Version | Release date | Major features, improvements | |
|---|---|---|---|
| Initial public release | |||
| 1.0 | [96] | First stable release | |
| 1.1 | [97] | Futures | |
| 1.2 | [98] | Protocols | |
| 1.3 | [99] | Enhanced primitive support | |
| 1.4 | [100] | Reader literals | |
| 1.5 | [101] | Reducers | |
| 1.5.1 | [102] | Fixing a memory leak | |
| 1.6 | [103] | Java API, improved hashing algorithms | |
| 1.7 | [104] | Transducers, reader conditionals | |
| 1.8 | [105] | Additional string functions, direct linking, socket server | |
| 1.9 | [106] | Integration with spec, command-line tools | |
| 1.10 | [107] | Improved error reporting, Java compatibility | |
| 1.10.1 | [108] | Working around a Java performance regression and improving error reporting from clojure.main | |
| 1.10.2 | [109] | Java interoperability/compatibility improvements and other important language fixes | |
| 1.10.3 | [110] | prepl support for reader conditionals | |
| 1.11.0 | [111] | New syntax for keyword argument invocation, new clojure.math namespace, namespace aliasing without loading, and new helper functions added to clojure.core | |
| 1.11.1 | [112] | Rolling back unintended change in binary serialisation of objects of types clojure.lang.Keyword and clojure.lang.ArraySeq. | |
| [113] | Fix for CVE-2024-22871 Denial of Service vulnerability | ||