extensible-compound-types
py4cl
extensible-compound-types | py4cl | |
---|---|---|
2 | 21 | |
10 | 223 | |
- | - | |
6.5 | 2.3 | |
3 months ago | 8 months ago | |
Common Lisp | Common Lisp | |
- | GNU General Public License v3.0 or later |
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.
extensible-compound-types
-
numericals - Performance of NumPy with the goodness of Common Lisp
Since the past year or two, I have been working on numericals that aims to provide the speed of NumPy with the goodness of Common Lisp. In particular, this includes the use of dynamic variables, restarts, and compiler-notes wherever appropriate. It uses CLTL2 API (and may be slightly more) under the hood to provide AOT dispatch, but nothing stops you from combining it with JAOT dispatch provided by numcl/specialized-function. This also spawned a number of projects most notably polymorphic-functions to dispatch on types instead of classes and extensible-compound-types that allows one to define user defined compound types (beyond just the type-aliases enabled by deftype. Fortunately enough, interoperation between magicl, numcl and numericals/dense-numericals actually looks plausible!
-
Compile-time array bound checks
(Shameless plug) I have recently been working on extensible-compound-types that might be useful. My main purpose with it was to bring "nice" custom array (and container) types without using satisfies-based hackery. But perhaps it can be put to use here.
py4cl
-
Need recommendation for IPC with Go
py4cl and cl4py rely on uiop:launch-program and python's subprocess respectively. These are portable to the extent uiop and subprocess are portable and do not require any additional installation.
-
Lisp-Stick on a Python
If you want to use Python libs from CL, see py4cl: https://github.com/bendudson/py4cl the other way around, calling your efficient CL library from Python: https://github.com/marcoheisig/cl4py/ There might be more CL libraries than you think! https://github.com/CodyReichert/awesome-cl (or at least a project sufficiently advanced on your field to join forces ;) )
-
The German School of Lisp (2011)
FYI you can call Python from CL: https://github.com/bendudson/py4cl and CL from Python: https://github.com/marcoheisig/cl4py/
If you don't know Emacs, see other editors: https://lispcookbook.github.io/cl-cookbook/editor-support.ht... If you want the more Smalltalk-like experience I'd go with the free LispWorks version: it has many GUI panes that allow to watch and discover the state of the program.
I personally couldn't stay long with Hylang. You won't get CL niceties: more language features, performance, standalone binaries, interactive debugger (all the niceties of an image-based development)…
-
Plotting
I ended up using a fair bit of matplotlib through college and with colleagues. I too don't want to use python, but I also don't like throwing away its libraries, and I'm too lazy to invest in other* plotting ecosystems. In effect, I use up using matplotlib through py4cl/2.
-
numericals - Performance of NumPy with the goodness of Common Lisp
Note that it is not my aim to replace the python ecosystem; I think that is far too lofy a goal to be of any good. My original intention was to interoperate with python through py4cl/2 or the likes, but felt that one needs a Common Lisp library for "small" operations, while "large" operations can be offloaded to python libraries through py4cl/2.
-
Good Lisp libraries for math
If performance is absolutely not a concern, then third option is using python libraries through py4cl/2. To put it differently, if calling python from lisp is not the bottleneck, then this is a feasible option.
-
Why Hy?
I encourage people to try out Common Lisp because, unlike with Hy, you will get: speed, ability to build binaries, truly interactive image-based development (yes, more interactive than ipython), more static type checks, more language features (no closures in Hy last time I checked), language stability… To reach to Python libs, you have https://github.com/bendudson/py4cl My comparison of Python and CL: https://lisp-journey.gitlab.io/pythonvslisp/
-
Tutorial Series to learn Common Lisp quickly
> Not sure if such a thing already exists for CL
couple of solutions exist for this
https://github.com/bendudson/py4cl
https://github.com/pinterface/burgled-batteries
- Calling Python from Common Lisp
-
(define (uwu) (display "nya~\n"))
Ahh, makes sense. Well, if you ever wanna steal some of python's thunder, libpython-clj worked great for me lol. Supposedly py4cl fills a similar role in Common Lisp.
What are some alternatives?
numericals - CFFI enabled SIMD powered simple-math numerical operations on arrays for Common Lisp [still experimental]
py4cl2 - Call python from Common Lisp
cl-cuda - Cl-cuda is a library to use NVIDIA CUDA in Common Lisp programs.
magicl - Matrix Algebra proGrams In Common Lisp.
hy - A dialect of Lisp that's embedded in Python
libpython-clj - Python bindings for Clojure
coalton - Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.
racket - The Racket repository
renegade-way - Option Trading Application
mgl - Common Lisp machine learning library.
cl4py - Common Lisp for Python
numcl - Numpy clone in Common Lisp