pika
A WIP little dependently-typed systems language (by naalit)
lisp
A lisp JIT compiler and interpreter built with cranelift. (by 0xekez)
pika | lisp | |
---|---|---|
4 | 5 | |
35 | 52 | |
- | - | |
7.1 | 0.0 | |
about 1 month ago | about 2 years ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | - |
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.
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.
pika
Posts with mentions or reviews of pika.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-01.
-
September 2021 monthly "What are you working on?" thread
I just switched Pika to using significant indentation. This is mostly because of how annoying line continuation is in a ML-style language (so f a b syntax) without significant indentation or required semicolons, but you can read more about the reasons for that decision in this section of the README.
-
May 2021 monthly "What are you working on?" thread
Recently, I've been working on adding garbage collection to Pika. I've successfully written an Immix-based garbage collector that works with the LLVM GC support infrastructure, and I'm currently working on integrating the GC with Pika, or really Durin, the dependently-typed intermediate representation that Pika compiles to. Because types are passed around at runtime, objects of unknown type and size can be stored unboxed in polymorphic data structures; but that makes keeping track of type information for heap allocations somewhat harder, because type information needs to be allocated and constructed at runtime in some cases. It's an interesting design problem, because you want constructing type information to be fast; but the GC will run much more often, so maximizing tracing speed by avoiding e.g. indirection in type information is important; and you also want to construct as much type information as possible at compile time and embed it as constants.
-
March 2021 monthly "What are you working on?" thread
I've been working on adding algebraic effects to Pika during the past month. It's turned out to be harder than I thought it would, but I'm almost done - performing and catching one effect at a time works, and the compilation strategy I'm using now (I reimplemented the whole thing after realizing the strategy I was using wouldn't actually work) should be enough to handle multiple effects at once and also effect polymorphism, I just have to get those working in the elaborator.
-
February 2021 monthly "What are you working on?" thread
After taking a break from Pika, my dependently-typed ML for systems programming, during the month of January, I've started working on it again by getting recursion to work properly. I'm planning on starting to implement algebraic effects next, and an Immix-based garbage collector for boxed values after that. Here's what my current plan for algebraic effects looks like:
lisp
Posts with mentions or reviews of lisp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-29.
-
GitHub - mcobzarenco/zee: A modern text editor for the terminal written in Rust
I've been curious about https://github.com/ezekiiel/lust but I don't know its status as a project
-
June 2021 monthly "What are you working on?" thread
Since last month I've been working on garbage collection and string handling in my Lisp compiler. I've found writing the garbage collector to be hard but strings are fun :)
-
May 2021 monthly "What are you working on?" thread
I just added variable-arity functions to my lisp which compiles to Cranelift. I was blocked for a while trying to work out how to convince Cranelift to put arguments on the stack but eventually gave up and I now heap allocate a location for function arguments. It's not great for performance but it feels great to have finally finished it!
-
February 2021 monthly "What are you working on?" thread
I’ve been carrying on working on compiling my lisp this month. It’s been a fun couple weeks because I’ve finally gotten to the fun stuff like higher order functions, closures, and adding the ability to call into libc.
What are some alternatives?
When comparing pika and lisp you can also consider the following projects:
konna - A fast functional language based on two level type theory
rust_lisp - A Rust-embeddable Lisp, with support for interop with native Rust functions
durin - the Dependent Unboxed higher-oRder Intermediate Notation
bread - An expression based scripting language
bluebird - A work-in-progess programming language modeled after Ada and C++
aulang - simple and fast scripting language
rumi - The rumi compiler
c3c - Compiler for the C3 language
starlight - JS engine in Rust
orion - Orion is a high level, purely functional programming language with a LISP based syntax.