access VS generic-cl

Compare access vs generic-cl and see what are their differences.

access

A common lisp library to unify access to common dictionary-like data-structures (by AccelerationNet)

generic-cl

Generic function interface to standard Common Lisp functions (by alex-gutev)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
access generic-cl
5 13
79 119
- -
0.0 0.0
over 1 year ago about 2 years ago
Common Lisp Common Lisp
GNU General Public License v3.0 or later 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.

access

Posts with mentions or reviews of access. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-20.
  • JZON hits 1.0 and is at last on the latest QL release: a correct and safe JSON parser, packed with features, and also FASTER than the latest JSON library advertised here.
    4 projects | /r/Common_Lisp | 20 Feb 2023
  • From Common Lisp to Julia
    6 projects | news.ycombinator.com | 8 Nov 2022
    I agree you can make arguments, I like your explanation for the final form further downthread. For the second form, another choice could be (.x foo) or (. foo x). Or if you're trying to write something like System.out.println("x"), Clojure's .. shows it could be written as (.. System out (println "x")). Or, if you're using CL, you can use the access library (https://github.com/AccelerationNet/access) and write things like #Dfoo.bar.bast or (with-dot () (do-thing whatever.thing another.thing)).

    In trying to further steelman a case where random Lisp syntax can be more difficult to read than, say, equivalent Python, two other areas come to mind. First is the inside-outness order of operations thing, it trips people up sometimes. Like the famous "REPL" (with a bad printer) is just (loop (print (eval (read)))), but in English we want to see that as LPER. Solutions include things like the arrow macro (Clojure did good work on showcasing it and other simple macros that can resolve this issue in many places) and if you write/pull one into CL REPL becomes (-> (read) (eval) (print) (loop)), how nice to read. But even the ancient let/let* forms allow you to express a more linear version of something, and you can avoid some instances of the problem with just general programming taste on expression complexity (an issue with all languages -- https://grugbrain.dev/#grug-on-expression-complexity ).

    The second area is on functions that have multiple exit points. A lot of Lispers seem to just not like return-from, and will convert things into cond expressions or similar or just say no to early-exits. The solution here I think comes from both ends, the first is a broader cultural norm spreading in other languages against functions with multiple return statements and getting used to code written that way, the other is to just not get so upset about return-from and use it when it makes the code nicer to read.

  • Document Store/DB Implemented in Common Lisp
    2 projects | /r/lisp | 1 Jun 2022
    thanks. Do you know how your cl-getx differs from access? https://github.com/AccelerationNet/access It is a universal accessor with the option of nested look ups.
  • Modern sequence abstractions
    4 projects | /r/Common_Lisp | 15 Jan 2022
    ps: related: how to access an element in all the lisp sequences, generically? I like access for that: https://github.com/AccelerationNet/access (and generic-cl

generic-cl

Posts with mentions or reviews of generic-cl. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-01.
  • Compiling a Lisp
    2 projects | news.ycombinator.com | 1 Feb 2024
    for those wanting generic +, equality and comparison in CL, there's a nice library: https://alex-gutev.github.io/generic-cl/
  • Adding new types and operators to Lisp
    6 projects | /r/lisp | 24 Feb 2023
    If performance is not a concern, then you can create CLOS classes corresponding to vec3 or mat44, and dispatch the appropriate functions from the generic-cl project by specializing on them.
    6 projects | /r/lisp | 24 Feb 2023
  • Emacs-like editors written in Common Lisp
    11 projects | news.ycombinator.com | 2 Oct 2022
    > And Lisp is almost uniquely able to handle transitions to later standards as I described above. You don't actually have to forfeit backwards compatibility entirely or at all if the changes are handled by moving to a new default base package. :cl-user/:cl become :cl##-user/:cl##

    Go use cl21[0] if you care for this sort of thing.

    > more generic functions would open up more interesting developments later

    generic-cl[1]. But in a prefix-oriented language, I just don't see this as particularly important.

    > you don't necessarily want to bless a particular concurrency model

    You do[2]; this is one of the notable deficiencies in the cl standard that really bites, today. It is being worked on.

    0. http://cl21.org/

    1. https://github.com/alex-gutev/generic-cl

    2. https://www.hpl.hp.com/techreports/2004/HPL-2004-209.pdf

  • From Common Lisp to Julia
    11 projects | news.ycombinator.com | 6 Sep 2022
    So, the article is harsh on CL: YMMV. Also, your goal may vary: I want to build and ship (web) applications, and so far Julia doesn't look attractive to me (at all). Super fast incremental development, build a standalone binary and deploy on my VPS or ship an Electron window? done. Problem(s) solved, let's focus on my app please.

    The author doesn't mention a few helpful things:

    - editor support: https://lispcookbook.github.io/cl-cookbook/editor-support.ht... Emacs is first class, Portacle is an Emacs easy to install (3 clicks), Vim, Atom support is (was?) very good, Sublime Text seems good (it has an interactive debugger with stack frame inspection), VSCode sees good work underway, the Alive extension is new, usable but hard to install yet, LispWorks is proprietary and is more like Smalltalk, with many graphical windows to inspect your running application, Geany has simple and experimental support, Eclipse has basic support, Lem is a general purpose editor written in CL, it is Emacs-like and poorely documented :( we have Jupyter notebooks and simpler terminal-based interactive REPLs: cl-repl is like ipython.

    So, one could complain five years ago easily about the lack of editor support, know your complaint should be more evolved than a Emacs/Vim dichotomy.

    - package managers: Quicklisp is great, very slick and the ecosystem is very stable. When/if you encounter its limitations, you can use: Ultralisp, a Quicklisp distribution that ships every 5 minutes (but it doesn't check that all packages load correctly together), Qlot is used for project-local dependencies, where you pin each one precisely, CLPM is a new package manager that fixes some (all?) Quicklisp limitations

    > [unicode, threading, GC…] All of these features are left to be implemented by third-party libraries

    this leads to think that no implementation implements unicode or threading support O_o

    > most of the language proper is not generic

    mention generic-cl? https://github.com/alex-gutev/generic-cl/ (tried quickly, not intensively)

    Documentation: fair points, but improving etc. Example of a new doc generator: https://40ants.com/doc/

    Also I'd welcome a discussion about Coalton (Haskell-like type system on top of CL).

  • Modern sequence abstractions
    4 projects | /r/Common_Lisp | 15 Jan 2022
    Does generic-cl work for you? In recent months, u/alex-gutev worked on it to separate it out into smaller subsystems.
  • Common Lisp polymorphic stories.
    13 projects | /r/lisp | 4 Nov 2021
    Anyway, this library is inspired by https://github.com/alex-gutev/generic-cl and provides polymorphic versions of many common standard functions based on types. For example, now `>` and `<` work on characters and strings as well, and `at` is a universal by-key accessor for all data structures (`aref` + `nth` + `gethash` + some more). It also tries to be as strictly typed as possible, resulting in compile-time errors/warnings in case types are mismatched. Types do not always need to be declared, they can be inferred thanks to excellent https://github.com/alex-gutev/cl-form-types by Alex Gutev. Besides that it includes a collection of useful macros for more "typey" style of coding as well as several data structures I consider missing from the standard. The structures are templated -- which means there's a structure type generated for each contained element-type.
    13 projects | /r/lisp | 4 Nov 2021
    Compared to generic-cls equality generic here: https://github.com/alex-gutev/generic-cl/blob/master/src/comparison/equality.lisp
  • alex-gutev/cl-form-types - Library for determining the types of Common Lisp forms based on information stored in the environment.
    2 projects | /r/Common_Lisp | 2 Jun 2021
    Thanks for sharing. I'm planning to use it in static-dispatch to further optimize generic function calls in generic-cl. It's also used in the lisp-polymorph project, work in progress not yet completed, which aims to provide an extensible generic interface, though not based on generic functions, to functions in the Common Lisp standard, like generic-cl however built from the ground up with performance and optimization and performance in mind.
  • Static-Dispatch 0.5: Improved inlining on SBCL and performance improvements for generic-cl
    3 projects | /r/Common_Lisp | 16 Apr 2021
    Release 0.5 adds a specialized implementation for SBCL which leverages the compiler's type inference engine, using DEFTRANSFORM, to allow for generic function inlining in a much broader range of scenarios. Any generic function call for which the types of the arguments can be determined by SBCL, can now be inlined by static-dispatch. This means even generic function calls with arguments consisting of complex expressions can be inlined. This also provides a performance boost for generic-cl where theoretically on SBCL, generic-cl:= should be equivalent in performance to cl:= in most cases where the type of the argument can be vaguely inferred by SBCL.

What are some alternatives?

When comparing access and generic-cl you can also consider the following projects:

coalton - Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.

static-dispatch - Static generic function dispatch for Common Lisp

reagent - A minimalistic ClojureScript interface to React.js

magicl - Matrix Algebra proGrams In Common Lisp.

inlined-generic-function - Bringing the speed of Static Dispatch to CLOS. Succeeded by https://github.com/marcoheisig/fast-generic-functions

drracket - DrRacket, IDE for Racket

trivia - Pattern Matcher Compatible with Optima

lisp-interface-library - LIL: abstract interfaces and supporting concrete data-structures in Common Lisp

fset - FSet, the functional collections library for Common Lisp.

specialized-function - Julia-like dispatch for Common Lisp

ctype - CL type system implementation

ccl - Clozure Common Lisp