durin
kesh
durin | kesh | |
---|---|---|
3 | 11 | |
13 | 19 | |
- | - | |
0.0 | 6.0 | |
about 2 years ago | 5 months ago | |
Rust | JavaScript | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
durin
-
Are there any low level, cross platform assembly languages that allow jumping to non labels?
So I think I may be one of the few people in the world who has actually implemented a GC using LLVM's statepoint infrastructure. It's poorly documented and there are some gotchas, but I'd say it's definitely usable, and it works with basically any collector design, including moving collectors (I'm using Immix) and has no runtime bookkeeping overhead and allows LLVM to optimize the code without worrying about GC, which is nice. It's actually gotten a bit better with LLVM 13, too. If you're curious what a LLVM-based GC looks like, mine is in this folder. Of course, if you just want some sort of GC, you can also just link it with Boehm which is quite easy and has pretty good performance - this is what e.g. Crystal does, although they're talking about switching.
-
September 2021 monthly "What are you working on?" thread
I also fixed lots of bugs in the GC and backend, so it should be a lot more stable now.
-
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.
kesh
- Have any of you designed a conlang, and then designed a programming language based on the conlang or any fictional culture that would use it?
-
Too many words about Rust's function syntax
I have something similar in kesh, where : is the assignment operator and the type/signature may be "assigned" before the value:
-
Temporal Programming, a new name for an old paradigm
I'm not OP, in case you thought that :) kesh lives here. I tried incorporating some of the ideas discussed here, but posponed it to a later language, which I'm still thinking about.
-
What language features do you "Consider Harmful" and why?
This is a great idea that I've adopted for my PL. I took it a step further and also allow extensions of the core language to be specified, including profiles.
-
Let's talk about interesting language features.
My (non-existing) language kesh, designed to compile to TypeScript, has expression blocks. That was one of my first decisions.
-
October 2021 monthly "What are you working on?" thread
Still no work on a compiler, but more work on the documentation of kesh.
-
What are some simple but powerful compile-to-JS languages I might not know about, or that you are working on (not Elm, Reason, PureScript, or ClojureScript)?
I'm working on kesh, but it's only at the design stage. I have tried to make it simple yet powerful, so I thought I'd mention it even though you can't use it.
-
Why are you building a programming language?
I tried to distill down the most essential features of TS/JS (functional, prototypal) and then come up with new syntax and semantics that was minimal, orthogonal and hopefully easy to learn and use. The result is kesh and na.
-
September 2021 monthly "What are you working on?" thread
I like the way you think. I had the same goal with kesh. A minimal syntax is easier on the eye and lets you focus on the actual code.
-
August 2021 monthly "What are you working on?" thread
I'm only at the drawing board stage of kesh, a simple little PL that one day might possibly transpile to TypeScript. Not a single line of compiler code has been written so far, it's still all about syntax design and exploring ideas. kesh is mostly a pastime activity and something I can ponder over when I'm bored or can't sleep (which may be the reason I can't sleep).
What are some alternatives?
c3c - Compiler for the C3 language
ric-script - A modern scripting language; implemented in old school C, yacc & flex
bluebird - A work-in-progess programming language modeled after Ada and C++
cubiml-demo - A simple ML-like programming language with subtyping and full type inference.
never - Never: statically typed, embeddable functional programming language.
ghc-proposals - Proposed compiler and language changes for GHC and GHC/Haskell
konna - A fast functional language based on two level type theory
na - a minimal data notation format
pika - A WIP little dependently-typed systems language
imp - Imp is a statically typed and compiled scripting language with the goal of increasing programmer confidence.
Cwerg - The best C-like language that can be implemented in 10kLOC.