deprecated-coalton-prototype
clisp
deprecated-coalton-prototype | clisp | |
---|---|---|
9 | 8 | |
216 | - | |
- | - | |
1.4 | - | |
over 2 years ago | - | |
Common Lisp | ||
MIT License | - |
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.
deprecated-coalton-prototype
-
The thing is, if you start with Common Lisp, it's pretty easy to write a DSL that adds the constraints and provides the guarantees that you need. [..] Maybe all I had to do to turn CL into Haskell is implement the Hindley-Milner algorithm.
can't jerk
-
Hell Is Other REPLs
I used to use CL quite a bit, but have since abandoned it for Haskell, so I'm a bit biased.
There's a number of issues with that:
- I'd be missing all the optimizations that can be performed due to purity.
- There's more to Haskell's type system than just vanilla Hindley-Milner, and the implementation of it isn't particularly trivial. https://github.com/stylewarning/coalton is the closest thing and it's still missing a large amount of the type system.
- Doing the implementation would be a significant amount of work to get it to integrate well with the language, and it would be a layer tightly glued on top instead of integrated with the language.
- A major part of Haskell is the standard library, a good chunk of the semantics of Haskell people use on a day to day basis, like monads and etc, are a part of the standard library.
-
Six years of professional Clojure development
This looks like something Common Lisp does better, however I have too little Clojure experience to compare. CL (and SBCL in particular) does "good enough" static type checks, it throws warning at compile time (when we compile one function with a keystroke). We can also precise our function types gradually. It isn't a HM type system (Coalton[1] could be it) but it's already great (compared to no compile-time types at all).
Oh, about interactive development: that's sure, CL shines here. Objects get updated (lazily) after a class change, we can install Quicklisp libraries without restarting the image, etc. It's very smooth.
1: https://github.com/stylewarning/coalton
- Common lisp or Racket as a first lisp?
- Coalton is a dialect of ML embedded in Common Lisp
- Coalton – a dialect of ML embedded in Common Lisp
-
What would you like to see in a CL dev environment?
Help out with Coalton.
-
Stupid protocols for CL - Is this a bad idea?
If you like this kind of stuff, maybe you can help implement type classes in Coalton.
-
On repl-driven programming
(there's a work-in-progress library to add a dialect of ML on top of CL: coalton)
clisp
-
Common Lisp Implementations in 2023
One should note that while it is true that the last CLISP release was a long time ago and there is not a lot of development going on right now, it's not dead. Bruno Haible just commited last week.
The repository is now at https://gitlab.com/gnu-clisp/clisp
-
Common Lisp implementations in 2023
CLISP is maintained here: https://gitlab.com/gnu-clisp/clisp/-/commits/master
-
clisp-head from Roswell now has support for package-local nicknames
Roswell has switched its clisp-head to be built from https://github.com/roswell/clisp/ which is based on the commits from CLISP's canonical repository along with patches which add package-local nicknames to it.
-
roswell (21.10.14.111-1): clisp-head support
Oh dang, there is new development on clisp! I had to do some digging to find [the repo](https://gitlab.com/gnu-clisp/clisp), but it looks like the latest commit even adds support for MacOS on ARM.
- Package local nicknames: don't use with quicklisp-targeted packages?
-
SICL: A New Common Lisp Implementation
> phoe got package local nicknames into all implementations
Unfortunately it's not yet in Clisp. I submitted a merge request[1] a year ago, but it's been silent since then.
[1]: https://gitlab.com/gnu-clisp/clisp/-/merge_requests/3
-
Common lisp or Racket as a first lisp?
Quick note, CLISP is actually an implementation of Common Lisp, and as such isn't used as an abbreviation for Common Lisp the language. Could you expand on what you mean w.r.t to package managers? As far as getting up and running with a CL environment, Portacle makes this pretty easy now.
What are some alternatives?
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
trivial-cltl2 - Portable CLtL2
immer - Postmodern immutable and persistent data structures for C++ — value semantics at scale
trivial-package-local-nicknames - Common Lisp PLN compatibility library.
yale-haskell - HASKELL: Yale Haskell system written in Lisp
ql-https - HTTPS support for Quicklisp via curl
kandria - A post-apocalyptic actionRPG. Now on Steam!
quicklisp-client - Quicklisp client.
clj-kondo - Static analyzer and linter for Clojure code that sparks joy
screenshotbot-oss - A Screenshot Testing service to tie with your existing Android, iOS and Web screenshot tests
austral - Systems language with linear types and capability-based security.
web-development-with-clojure - Repository for the examples from the book Web Development with Clojure, 2nd edition