sealable-metaobjects
A CLOSsy way to trade genericity for performance. (by marcoheisig)
abstract-arrays
A structure and some facilities for an abstract-array structure in common lisp (by digikar99)
Our great sponsors
sealable-metaobjects | abstract-arrays | |
---|---|---|
2 | 1 | |
34 | 2 | |
- | - | |
10.0 | 5.1 | |
almost 4 years ago | 20 days ago | |
Common Lisp | Common Lisp | |
MIT License | - |
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.
sealable-metaobjects
Posts with mentions or reviews of sealable-metaobjects.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-04.
-
Eliminating CLOS for a 4.5x speedup
I wonder if things like https://github.com/marcoheisig/sealable-metaobjects would help with the speed while keeping the CLOSiness.
-
Common Lisp polymorphic stories.
About static typing and generic functions, are there limitations to fast-generic-functions built over sealable-metaobjects too? I felt that reasonable, albeit it takes away the dynamic nature of the objects after sealing.
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 sealable-metaobjects and abstract-arrays you can also consider the following projects:
lisp-interface-library - LIL: abstract interfaces and supporting concrete data-structures in Common Lisp
ccl - Clozure Common Lisp
ctype - CL type system implementation