koka

Koka is still pretty much one person's project [0], and it's not for lack of PRs [1]. To push Koka forward at the kind of pace that Richard wants to move would require forking it or commandeering it, and it makes total sense that neither option is as appealing as just starting fresh. [0] https://github.com/koka-lang/koka/graphs/contributors [1] https://github.com/koka-lang/koka/graphs/contributors

> This idea is so simple, so crazy, so stupid, and works so well, but I never thought of it. Bravo to the authors. Thanks for the nice summary -- looking forward to read the paper! The same idea of self-tagging is actually also used in Koka language [1] runtime system where by default the Koka compiler only heap allocates float64's when their absolute value is outside the range [2e-511,2e512) and not 0, infinity, or NaN (see [2]). This saves indeed many (many!) heap allocations for float intensive programs. Since Koka only uses 1 bit to distinguish pointers from values, another slightly faster option is to only box negative float64's but of course, negative numbers are still quite common so it saves less allocations in general. [1] https://koka-lang.github.io/koka/doc/book.html#sec-value-typ... [2] https://github.com/koka-lang/koka/blob/d

This post by the Koka-author is an update about what's currently being worked on: https://github.com/koka-lang/koka/discussions/339

Maybe Lobster could be an option. https://strlen.com/lobster/ https://aardappel.github.io/lobster/memory_management.html It uses compile-time reference counting / lifetime analysis / borrow checking. Which is mostly inlined to the point that there is none of the sort in the compiled output and objects can even live on the stack. It basically looks like Python but is nothing like it underneath, and of course with no GIL. You can run it on JIT or compile it to C++. There's also Koka with the Perceus algorithm on compile time and looks like a much cleaner language than Rust. It also tracks side effects of every function in a type where pure and effectful computations are distinguished. https://github.com/koka-lang/koka

I have a toy language I play around with that's just in specifications stage. Not mine but an interesting compile-to-c language: https://github.com/koka-lang/koka. Functional, effects, no-GC.

Yes, see this Github Discussion for more context: https://github.com/koka-lang/koka/discussions/339#discussion... > yes! Currently the active development is in dev-fbip, see also our recent tech report: https://www.microsoft.com/en-us/research/publication/fp2-ful... We hope to put out a fresh release after the POPL deadline (Jul 11) that will include the new fip keyword and other goodies.

Some programming language like JS, use path-based imports, that's not good for making a stabel API. See https://api-extractor.com/pages/setup/configure_rollup/#:~:text=(The%20API%20Extra… And https://github.com/koka-lang/koka/issues/31#issuecomment-1482200826

So many new programming languages coming up with clever features that makes me wish I could mix and match their core features while using libraries from more popular languages. Up and coming Languages I am excited about - 1. Roc - https://www.youtube.com/watch?v=vzfy4EKwG_Y 2. Zig - https://ziglang.org/ 3. Scopes - https://sr.ht/~duangle/scopes/ 4. Gleam - https://gleam.run/ 5. Odin - https://github.com/odin-lang/Odin 6. Koka - https://github.com/koka-lang/koka 7. Unison - https://github.com/unisonweb/unison

You might be interested in the FBIP versions of Okasakis datastructures in https://github.com/koka-lang/koka/tree/master/test/perf/sets Most of them only have 'insert' and 'lookup', but they are ~10% faster than Okasakis versions. For red-black trees in particular the fastest implementation is https://github.com/koka-lang/koka/blob/master/test/bench/kok...

So I would say this echoes my experience with it so far -- it is definitely a work in progress! However, I tend to approach Koka as if it were Standard ML with an effect system (up to a point), so the lack of a full imperative API hasn't been felt too much. I am more missing ad-hoc polymorphism than imperative tooling. I am not sure I understand your comment about mut variables; my understanding is there are two types of mutable variables in Koka -- 'local' and 'ref'. 'local' is a locally mutable variable, and 'refs' are globally shareable. A 'ref' can be shared between functions, 'local' is just to give an imperative API using mutable variables. How 'local' works kind of confuses me so I tend to avoid it altogether in favour of local names (i.e. 'val' rather than 'var') and tail recursion (instead of loops with mutation). 'ref' seems qui

How does this compare to other effect-oriented languages like Koka, Frank, and Eff? I've been doing some work with Koka lately, but I briefly looked into the other three (including Effekt) and it mostly came down to, 'Koka seems most active in development'[1] and 'Koka had the easiest to use documentation for me'[2], which are both kind of subjective ways of choosing between them rather than an objective comparison. [1] E.g. https://github.com/effekt-lang/effekt had its last commit back in June; https://github.com/frank-lang/frank last commit last year; but https://github.com/koka-lang/koka last update was Oct 15. Effekt seems semi-active, at least, compared to Frank. While stability is good, I wouldn't expect it in a language actively being used for research. [2] Comparing https://koka-lang.github.io/koka/doc/book.html and https://effekt

Huh, now I'm curious whether it means 2x or 1.5x. These graphs on the github look promising https://github.com/koka-lang/koka/blob/master/doc/bench-amd3...

Its not like Microsoft does not work on that, they probably have a dozen different formally verified programming languages around at the moment. You already mentioned F*[0], but there is also Checked C[1], VCC[2], koka[3], dafny[4], Project Verona and probably some more that I am missing. The point being that they have clearly evaluated and have used F-Star for parts of the OS already. [0]: https://www.fstar-lang.org [1]: https://www.microsoft.com/en-us/research/project/checked-c/ [2]: https://www.microsoft.com/en-us/research/project/vcc-a-verif... [3]: https://github.com/koka-lang/koka [4]: https://github.com/dafny-lang/dafny [5]: https://www.microsoft.com/en-us/research/project/project-ver...