Clojure

The registry row this page is generated from

Read at render time from the same family row the register reads, so nothing in this block can disagree with it.

Extensions

.clj, .cljs, .cljc, .edn

Registry names

clojure

Recorded symbols

namespaces · functions · protocols

Relationship types this analyzer constructs

11 of 14 constructed, read from this analyzer's source and re-derived by the languages gate. Each row below is one of the engine's types, in the engine's own order.

11 constructed, 3 not constructed. All 3 absent types are recorded as ruled absent: the written reason and the corpus measurement behind each are in this family's completeness record. The register explains what each label means.

What this analyzer does not resolve

• A call to clojure.core is suppressed unless this namespace declares or refers that name, and the check is position-aware: a form above (defn map ...) really is the standard library while one below it is the file's own var. The exclusion list holds 723 names.
• recur is a special form that transfers control to the enclosing fn — it names no var and invokes nothing — so it produces no edge, and neither does a call whose name was minted for an anonymous function.
• There is no override edge, and that is a fact about Clojure: a defmethod introduces a var sharing a name with the multimethod rather than replacing a member of anything, so there is no override to record.

Every line above was written against Clojure’s own analyzer module and is named against a construct in it, so it can be checked against the source. Nothing here is inherited from a template, or from another language’s page.

Where you meet it in a repository

Recognised by extension — .clj, .cljs, .cljc, .edn. Everything below is about where those files actually sit in a working repository.

• A Clojure codebase is one file per namespace, and the :require form at the top is the only statement that says where anything came from.
• Protocols are usually defined next to the functions they dispatch on, while the implementations live wherever the concrete type does.
• Test namespaces use deftest, which bb records as a function, so test bodies are indexed alongside the code they exercise.

Questions this index answers

Phrased as retrievals, because that is what an index can honestly do: it holds the symbols and the edges between them, and hands them back with the evidence attached.

1. Which namespaces require this library?
2. Which names does this namespace refer from another one?
3. Which records implement this protocol?
4. Which functions does this namespace declare, macros included?

What the analyzer sees in code like this

(ns myapp.cart
  (:require [myapp.account :as acct]))

(defrecord Cart [id total])      ; bb records: type Cart · fields id, total

(defn place [cart user]           ; bb records: function place
  (acct/charge! user (:total cart)))   ; bb records: a call through the alias

Symbols are stored with the file they came from and the bytes they span, so a hit points at a line rather than at a guess. The annotations in the sample are commentary for the reader, not strings the index would store.

Languages that turn up in the same repository

Functional & declarative — the count beside each name is how many relationship types that family’s analyzer constructs.

• Elixir10 types
• Haskell12 types
• Scala11 types
• Erlang9 types
• F#11 types
• Clean9 types
• Nim12 types
• Julia11 types
• MATLAB11 types
• Solidity11 types