lisp-interface-library VS sealable-metaobjects

Compare lisp-interface-library vs sealable-metaobjects and see what are their differences.

lisp-interface-library

LIL: abstract interfaces and supporting concrete data-structures in Common Lisp (by fare)

sealable-metaobjects

A CLOSsy way to trade genericity for performance. (by marcoheisig)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
lisp-interface-library sealable-metaobjects
1 2
145 34
- -
4.0 10.0
9 months ago almost 4 years 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.

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.
    13 projects | /r/lisp | 4 Nov 2021
    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?

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
    1 project | /r/Common_Lisp | 24 Dec 2022
    I wonder if things like https://github.com/marcoheisig/sealable-metaobjects would help with the speed while keeping the CLOSiness.
  • Common Lisp polymorphic stories.
    13 projects | /r/lisp | 4 Nov 2021
    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.

What are some alternatives?

When comparing lisp-interface-library and sealable-metaobjects you can also consider the following projects:

ccl - Clozure Common Lisp

ctype - CL type system implementation

fast-generic-functions - Seal your generic functions for an extra boost in performance.

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.

polymorph.maths - Maths for polymorph.stl

abstract-arrays - A structure and some facilities for an abstract-array structure in common lisp

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.