https://github.com/guicho271828/data-structures-in-common-lisp

A survey of data structure availability / quality in common lisp
https://github.com/guicho271828/data-structures-in-common-lisp

Last synced: 29 days ago
JSON representation

A survey of data structure availability / quality in common lisp

• Host: GitHub
• URL: https://github.com/guicho271828/data-structures-in-common-lisp
• Owner: guicho271828
• Created: 2016-03-18T13:00:27.000Z (almost 9 years ago)
• Default Branch: master
• Last Pushed: 2016-04-09T09:26:50.000Z (over 8 years ago)
• Last Synced: 2024-10-15T14:11:00.457Z (3 months ago)
• Language: Common Lisp
• Size: 4.88 KB
• Stars: 2
• Watchers: 5
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.org

Awesome Lists containing this project

README

        
* data-structures-in-common-lisp

This is a repository containing a survey of data structure availability / quality in Common Lisp.

For computer scientists, efficient implementations of some key data structures are the must.

Thanks to quicklisp, currently there are bunch of libraries available.

However, their quality varies --- some may use CLOS, some may be imperative, some are missing documentations.

To contribute, add a new entry to =database.sexp=. *Currently, no explicit format is specified.* They are not processed by any programs. Just follow the other entries, and you may extend the format. Example:

#+begin_src lisp

(:hh-redblack

 :provides (:red-black-tree)

 :features (:persistence :clos)

 :documentation :missing

 :status (:non-usable :outdated))

#+end_src

* background

This project is somewhat similar in spirit to

http://eudoxia.me/article/common-lisp-sotu-2015/ . However, I do not plan

to propose any consolidation mainly because I believe the data structure

availability in common lisp is low, rather than "too high" that it is

difficult to choose which one to settle on, as in the case of application

tools such as web server, databases, GUI.

I emphasize that I am not a sort of Data Structure Ninja and

any contributions are welcome. However, I do not like to make this tiny project like

Cliki, which contains bunch of outdated, unorganized information.

So, the material in the survey should better be a library already available in quicklisp.