Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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.)
Related posts
- Carp: A statically typed Lisp, without a GC, for real-time applications
- Ask HN: Looking for statically typed, No-GC and compiled Lisp/scheme
- NASA just sent a software update to a spacecraft 12B miles away
- Carp
- Yet nobody questions ABAP, Lua, Julia, Groovy or Scala, both of them are under Lisp in TIOBE Index