Evergreen Common Lisp
github.com/atgreen/evergreen- Category
- Developer Tools
- Rank
- No. 3680Tools index
Previous survey · No. 3510 ·
- Type
- TOOL
- Use case
- Coding
- GitHub
- 67 stars
- Latest release
- v0.0.11
- Date
About
Evergreen is a Common Lisp implementation inspired by the HotSpot JVM, with tiered JIT compilation and on-stack replacement. It also lists fibers, JVM integration, static and dynamic linked binaries, tree-shaking, and speculative optimization with deoptimization. Native Android apps can be built directly from asdf and connected to with sly. It is at v0.0.1 and the author says it is still early.
At a glance
Evergreen Common Lisp is an experimental Lisp implementation written in Rust. Supported code moves from bytecode into native compilation as it becomes hot, while unsupported forms can use an evaluator fallback. It also explores saving a Lisp environment and removing unused code when delivering an executable.
Good fit
Spend time on it if you want to investigate runtime design, adaptive compilation or how a new Lisp implementation handles real programs. The documentation explains execution tiers and their current boundaries. A small expression and one library you actually need will tell you more about fit than a feature checklist.
Consider something else when
You need production readiness, complete ANSI Common Lisp conformance or stable compatibility with existing libraries. The project explicitly promises none of those. A listed runtime target also does not mean it has the same native compiler, foreign-library support or validation as the main Linux target.
Start here
On a supported installation, run egcl --no-init --eval with the expression (+ 1 2); the documented result is 3. Then try a short program and a local ASDF system before evaluating executable delivery. For source builds, follow the checkout’s pinned Rust toolchain rather than overriding it with the newest compiler.
Cost and requirements
The runtime declares GPL-3.0-or-later with the Classpath Exception; its exception distinguishes independent application modules from changes to Evergreen itself. Published native packages target Fedora 44 x86-64. Source builds need Git, a C toolchain and pinned Rust 1.94.1; macOS arm64 uses an explicit target and has a narrower validation baseline.
Limits to know
Compiler coverage is partial, so one process may mix native, bytecode and evaluator execution with different performance. Default static-musl builds have more limited shared-library compatibility than the Fedora glibc package. The embedding/iOS documentation is explicitly source-only and unexecuted; it does not establish a working mobile runtime, restartability or containment of native faults.
Sources checked 2026-10-30. Source-based assessment.
- github.com/atgreen/evergreen/blob/main/README.md
- github.com/atgreen/evergreen/blob/main/Cargo.toml
- github.com/atgreen/evergreen/blob/main/docs/overview.md
- github.com/atgreen/evergreen/blob/main/docs/embedding.md
- github.com/atgreen/evergreen/blob/main/crates/egcl/src/main.rs
- github.com/atgreen/evergreen/blob/main/rust-toolchain.toml
- github.com/atgreen/evergreen/blob/main/LICENSE.classpath-exception
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.