jank-lang/jank

jank is the native Clojure dialect with seamless C++ interop.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 20th, 2026
Created on July 2nd, 2014
Open Issues & Pull Requests: 76 (-1)
GitHub issues: Enabled
Number of forks: 132
Total Stargazers: 3,332 (+0)
Total Subscribers: 43 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 69
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 371 days
Stale 30+ days: 52
Stale 90+ days: 49

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • category:compiler (111)
  • help wanted (102)
  • category:runtime (35)
  • category:distribution (19)
  • category:tooling (11)
  • category:clang (8)
  • needs:research (7)
  • category:clojure-test-suite (5)

Detailed Description

jank is a native Clojure dialect that compiles to LLVM with seamless C++ interop.

jank addresses the tension between Clojure's interactive, functional, value-oriented programming model and the need for native runtime performance. Where Clojure targets the JVM with Java interoperability, jank targets LLVM with C++ interoperability. The language aims for strong compatibility with Clojure while delivering the performance characteristics of compiled native code. It uses a compiler architecture built on LLVM to translate Clojure-like syntax into efficient machine code.

jank suits developers who want Clojure's expressive functional paradigm but need the performance profile and direct system-level access that C++ interop provides. It is appropriate for projects where JVM startup time, garbage collection pauses, or memory overhead are constraints, or where tight integration with existing C++ codebases is required. The project is in alpha, so it is best suited for exploratory work and projects where stability is not yet a hard requirement. The README does not position jank against other Clojure implementations or native language alternatives, so no comparative claims can be made.

Development activity shows consistent engagement with the codebase through regular commits and active CI workflows. The project maintains test coverage tracking and has established community channels for discussion. Sponsorship support from organizations and individuals indicates sustained backing for the work.