ctype
Cleavir
Our great sponsors
| ctype | Cleavir | |
|---|---|---|
| 2 | 3 | |
| 25 | 45 | |
| - | - | |
| 6.2 | 6.6 | |
| 21 days ago | 3 months ago | |
| Common Lisp | Common Lisp | |
| BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ctype
-
Re-targeting (Lisp) compilers
There is significant overlap with SICL and its associated pieces which supply many of the other parts needed to make a Common Lisp. Some of these are Cluster which provides a portable and extensible assembler, Eclector which supplies a portable and extensible reader, Concrete-Syntax-Tree that supports source code tracking during compilation, ctype that implements the Common Lisp type system, and Clostrum that provides first-class environments for e.g. run-time, evaluation, and compilation. The SICL project has as one of its goals the creation of portable infrastructure for implementing Common Lisp, and these pieces are novel building blocks that were created as part of the project.
-
Common Lisp polymorphic stories.
Other times, the support is limited by the implementations supported by ctype and cl-form-types (and cl-environments). Although, if there is any good request, I could work on making a dynamic-only ANSI-CL compliant sub-system of PF.
Cleavir
-
Re-targeting (Lisp) compilers
Clasp notably uses Cleavir which is “an implementation-independent framework for creating Common Lisp compilers”.
-
Flexible intrinsics for my minimal code generator
I think something similar has come up with the Cleavir framework; there are currently separate instruction types for arithmetic operations, but it has been proposed to replace them with fewer types, because there is little use in specific types. Register allocation is specified the hard way currently, while as you say, the complexity even for x86-64's multiplication and division instructions is just in forcing use of the right input and output registers.
-
Clasp reaches 1.0 (Common Lisp with C++ Interop)
This is a project that has been in development for years now and also makes use of the Cleavir compiler framework (https://github.com/s-expressionists/Cleavir), which is being developed as part of another new Common Lisp implementation called SICL (https://github.com/robert-strandh/SICL).
Congrats to the CLASP devs, this is a huge accomplishment and it's really exciting to see a new CL implementation get a 1.0 release.
What are some alternatives?
fast-generic-functions - Seal your generic functions for an extra boost in performance.
SICL - A fresh implementation of Common Lisp
lisp-interface-library - LIL: abstract interfaces and supporting concrete data-structures in Common Lisp
Clostrum - First Class Global Environments
sealable-metaobjects - A CLOSsy way to trade genericity for performance.
Eclector - A portable Common Lisp reader that is highly customizable, can recover from errors and can return concrete syntax trees
polymorphic-functions - A function type to dispatch on types instead of classes with partial support for dispatching on optional and keyword argument types.
Concrete-Syntax-Tree - Concrete Syntax Trees represent s-expressions with source information
generic-cl - Generic function interface to standard Common Lisp functions
ccl - Clozure Common Lisp