Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/guicho271828/common-lisp-extensions
list of extensions beyond CL available in lisp implementations, and the status of its spread.
https://github.com/guicho271828/common-lisp-extensions
Last synced: 29 days ago
JSON representation
list of extensions beyond CL available in lisp implementations, and the status of its spread.
- Host: GitHub
- URL: https://github.com/guicho271828/common-lisp-extensions
- Owner: guicho271828
- Created: 2019-05-19T06:31:22.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-05-19T12:40:03.000Z (over 5 years ago)
- Last Synced: 2024-10-15T14:11:00.715Z (3 months ago)
- Size: 6.84 KB
- Stars: 21
- Watchers: 8
- Forks: 0
- Open Issues: 34
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# common-lisp-extensions
List of extensions beyond CL available in lisp implementations, and the status of its spread.
The progress can be seen in [the "Github Projects" page](https://github.com/guicho271828/common-lisp-extensions/projects/1).
**This is a leaderboard for tracking the progress across implementations, not a place to post your new ideas. Unimplemented features will be closed immediately.** But you can fork an existing Lisp implementation to implement your idea and make a proposal here.If you know any extentions that are not included in the learderboard, please make a new issue thread.
"Extensions" refers to the additional features implemented in the functions and macros in the `:common-lisp` package,
not the libraries based on the implementation-specific functions. For example, CAPI in Lispworks does not count as the
language extensions of CL.Syntactic constructs implemented with macros on top of CL do not count as the "Extensions" either. Therefore, most public libraries
that provide macros are not considered "extensions" in this repository's term.Similarly, simple reader macros (such as hash-table literals) are not considered "Extensions". However, features that require significant changes in the reader algorithm, such as package prefixed sexp and local package nickname, are considered extensions.
Compiler features are considered as "extensions". For example, `sb-ext:*inline-expansion-limit*` is an example of compiler extensions.