inko
By gitlab-inko-lang
sbcl
Mirror of Steel Bank Common Lisp (SBCL)'s official repository (by sbcl)
inko | sbcl | |
---|---|---|
9 | 60 | |
- | 1,781 | |
- | 1.0% | |
- | 9.9 | |
- | 1 day ago | |
Common Lisp | ||
- | 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.
inko
Posts with mentions or reviews of inko.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-26.
-
v0.10.0 of Inko, a statically typed language written in Rust, is released
Performance at the moment is a bit iffy. In theory Inko should be able to outperform Wren and Lua, but in practice method calls are a bit too expensive due to how stack frames are managed (see this issue for some details). Adding a set of benchmarks is definitely something I want to do, but I just haven't gotten to it yet.
- After 1.5 years of work, Inko's single ownership and concurrency changes are merged
-
How to write a compiler or interpreter in rust
You can use Inko as a reference, as its VM is written in Rust. I do recommend using this branch instead of the latest release, as there are a lot of upcoming changes to the language as a whole.
-
Implicit Overflow Considered Harmful (and how to fix it)
Code wise it requires either a ton of code, or a whole bunch of macros. I used the latter approach (see here). Even after optimising this, you'll still end up with a bucket of extra code/macros.
-
Root scope of language when implementing standard library vs using the language anywhere else.
Various modules use VM instructions to access built-in functionality, such as adding integers. Here is an example. The compiler transforms these into actual instructions (bytecode wise). So _INKOC.foo_bar basically means "run the foo_bar instruction".
-
What are the best ways programming languages address and solve the expression problem?
Probably the most common approach in a statically typed language is to use some form of pattern matching. For Inko I do exactly that in its type checker (example here). Prior to this I was using the visitor pattern using double dispatch, but this was painful to work with. The pattern matching approach is type-safe, quite easy to extend, and easy to wrap your head around.
-
Fun with IP address parsing
I wrote some IPv4 and IPv6 parsing code before, but wasn't aware of the various crazy IPv4 formats.
-
Inko 0.9.0 released, featuring generators, pattern matching, the removal of nullable types, a brand new manual, and much more
Resuming a generator is pretty simple too: take the generator, swap it with the current one, then set its parent to the previous generator (the one we just swapped out).
sbcl
Posts with mentions or reviews of sbcl.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-28.
-
Arena Allocation in SBCL
Based on the commit message [0], and the references to "user code" in this document, my guess is that user programs have or will have access, but it's not finalized enough to be documented.
That being said, I suppose if you're developing an internal API for a compiler/interpreter, your "users" could be other parts of the project rather than language users.
https://github.com/sbcl/sbcl/commit/7f65522a16d857e41aa61cd0...
-
Steel Bank Common Lisp 2.3.8 released: “a mark-region parallel GC is available”
See for example:
https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...
- Implementing Interactive Languages
-
Garbage Collection in a Large Lisp System (1984) [pdf]
related: the Immix inspired parallel-mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently into SBCL.
https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...
https://applied-langua.ge/~hayley/swcl-gc.pdf
build with
./make.sh --without-gencgc --with-mark-region-gc (on x86-64/Linux and x86-64/macOS only at the moment).
-
SBCL: merge of mark-region GC
The Immix inspired mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently, which is pretty cool news for SBCL users.
- Owner of Symbolics Lisp machines IP is interested in a non-commercial release
- Steel Bank Common Lisp