lisp-interface-library
LIL: abstract interfaces and supporting concrete data-structures in Common Lisp (by fare)
abstract-arrays
A structure and some facilities for an abstract-array structure in common lisp (by digikar99)
Our great sponsors
| lisp-interface-library | abstract-arrays | |
|---|---|---|
| 1 | 1 | |
| 145 | 2 | |
| - | - | |
| 4.0 | 5.1 | |
| 9 months ago | 18 days ago | |
| Common Lisp | Common Lisp | |
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
lisp-interface-library
Posts with mentions or reviews of lisp-interface-library.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-04.
-
Common Lisp polymorphic stories.
What are your thoughts on the Lisp Interface Library? I recognize that it doesn't cover some of your use cases since LIL is designed in a dynamic manner and does not provide the sort of compile-time type shenanigans that coalton can. Just from the standpoint of providing parametric polymorphism though, dynamic or not, what do you think of it?
abstract-arrays
Posts with mentions or reviews of abstract-arrays.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-04.
-
Common Lisp polymorphic stories.
And, there won't be a way to properly understand what exactly PF (or CL) misses without immersing myself into a ML-style something, is there? As in, I get some parts of what you are saying; I myself had to (ab)use deftype and gensym intern for another library for providing (limited) parametric types; but I also fail to see something seriously wrong with it, given that it plays nicely with cl:declare, cl:typep and cl:subtypep for the primitive use case of single value type checking, declaration and with some additional things (compiler)macro based optimization.
What are some alternatives?
When comparing lisp-interface-library and abstract-arrays you can also consider the following projects:
ccl - Clozure Common Lisp
fast-generic-functions - Seal your generic functions for an extra boost in performance.
ctype - CL type system implementation
generic-cl - Generic function interface to standard Common Lisp functions
polymorphic-functions - A function type to dispatch on types instead of classes with partial support for dispatching on optional and keyword argument types.
sealable-metaobjects - A CLOSsy way to trade genericity for performance.
polymorph.maths - Maths for polymorph.stl
cl-form-types - Library for determining the types of Common Lisp forms based on information stored in the environment.
coalton - Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.
lisp-interface-library vs ccl
lisp-interface-library vs fast-generic-functions
lisp-interface-library vs ctype
lisp-interface-library vs generic-cl
lisp-interface-library vs polymorphic-functions
abstract-arrays vs ccl
lisp-interface-library vs sealable-metaobjects
lisp-interface-library vs polymorph.maths
lisp-interface-library vs cl-form-types
lisp-interface-library vs coalton