Carp Alternatives
Similar projects and alternatives to Carp
-
-
-
OPS
OPS - Build and Run Open Source Unikernels. Quickly and easily build and deploy open source unikernels in tens of seconds. Deploy in any language to any cloud.
-
Nim
Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
-
-
-
-
ferret
Ferret is a free software lisp implementation for real time embedded control systems. (by nakkaya)
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
-
-
-
-
-
-
-
-
-
-
FunGEn
A lightweight, cross-platform, OpenGL-based 2D game engine in Haskell (by haskell-game)
-
-
Reviews and mentions
-
What is haskell used for ?
Haskell happens to be one of the most hard-core functional languages, which brings some interesting features to the table. It's used a lot for academic research, writing compilers for other languages (e.g. Carp, Idris etc.), it's used for making generative art and music, or by many large companies and startups in the financial and tech sectors. Most famously, Facebook uses Haskell for its spam detection algorithms.
-
The Clojure Mindshare (2019)
I love Clojure, but I do miss static types. I'm hoping Carp[0] (mentioned in the article) comes into its own. It seems like it could become my ideal language. The other problem I have with lisps in general is that they seem to encourage clever programming that is hard to read / debug (or maybe they just attract developers who value brevity over clarity... not sure).
-
Bubbleos, a Self-Contained OS
In the “Immediate plans (say, March 2019)” (yes, most of this project is 2¾ years old, though there have been spasms of activity in some areas from time to time since):
> Leconscrip: a memory-safe low-level statically-typed imperative language without garbage collection and with Lisp syntax, […]
I think producing anything even vaguely useful of this description in under a month was fairly wildly unrealistic. The only path to memory safety without garbage collection (… unless you’re willing to forego references altogether, which would generally disqualify usefulness) is some form of ownership tracking, and that’s a fairly lightly-trodden and lightly-documented path. There are very few examples of such languages even if you skip Lispness—I think Cyclone was the first (a research project spanning 2001–2006; and correct me if there was prior art), and Rust is the only even vaguely mainstream one. Making a language with these features using Lisp syntax (which I presume to include macros, otherwise is it even Lisp syntax?) is even more lightly-trodden and I suspect more difficult on average, though Carp <https://github.com/carp-lang/carp> looks to be having a go at that.
(I’m definitely interested in the concept of a memory-safe, garbage-collection-free language with Lisp syntax. I wish Carp and any other attempts well.)
- Clojure, but without the JVM?
- Carp - A statically typed lisp, without a GC, for real-time applications.
-
Hacker News top posts: Oct 15, 2021
Carp – A statically typed Lisp, without a GC, for real-time applications\ (67 comments)
-
Carp – A statically typed Lisp, without a GC, for real-time applications
An overview of it's deficiencies: https://github.com/carp-lang/Carp/issues/1317
Lisp is not necessarily functional. There's a lot of mutation in Common Lisp even if the community favors a functional style.
I think the question is: how does Lisp function without garbage collecting cons cells?
Carp language guide states lifetimes are statically inferred [1] which my guess is they allocate on stack (or malloc/free by scope) and detect use-after-free at compile time.
Another, more theoretical approach is using linear types which require all values to be "consumed" [2]
1: https://github.com/carp-lang/Carp/blob/master/docs/LanguageG...
2: https://www.cs.utexas.edu/users/hunt/research/hash-cons/hash...
Of course the obvious question is "What kind of memory management does it use?"
It uses a "linear" (actually affine) type system for memory management, with borrowed refs similar to Rust, but evidently without tracking mutability: https://github.com/carp-lang/Carp/blob/master/docs/Memory.md
So "cons", and the associated "car" and "cdr" functions are innately the "thing" that needs to be garbage collected in Lisp-like languages.
So I immediately went to the manual, and CTRL+F'd for cons. Carp has the following restriction: https://github.com/carp-lang/Carp/blob/master/docs/Manual.md
> If you're calling a dynamic function (something defined with defndynamic, or a built in command) it will be executed right away. This works very much like a classic, dynamically typed Lisp interpreter. The dynamic functions are not available in compiled code! Their main usage is in macros and to programatically control your build settings.
cons, car, and cdr are all "Dynamic" functions that can only run _DURING COMPILE TIME_. Which means the GC is not needed during runtime: all garbage-collection occurs in the compiler.
- Carp: A statically typed lisp, without a GC, for real-time applications
Stats
carp-lang/Carp is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.