Installer koka avec Homebrew, apk, Nix

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• koka

Historique du projet

Microsoft Research records the Koka project as established on 2012-04-13. Daan Leijen's project materials describe it as a strongly typed functional-style language with effect types and handlers, using a small core of composable language features rather than many special-case extensions.

Koka's early academic identity was tied to row-polymorphic effect types. The 2014 paper 'Koka: Programming with Row-polymorphic Effect Types' describes Koka as implementing the effect system and being used for small to medium examples. Later work pushed effect handlers and efficient implementation techniques, including 2021 ICFP work on generalized evidence passing for effect handlers.

The v3 documentation dated 2026-03-17 describes Koka v3 as a research language under development, stable enough that the compiler implements the full specification, but lacking mature async libraries and package management. That positioning explains why package-manager availability is useful even though the language is not a broad application platform.

Historique d'adoption

Koka's adoption is primarily academic and experimental. It is used to explore effect typing, handlers, Perceus optimized reference counting, reuse analysis, and functional-but-in-place programming ideas rather than to anchor a large industrial ecosystem.

Homebrew, Alpine, and Nix packaging make it easier for programming-language researchers, students, and curious developers to run the compiler without building the Haskell/C toolchain path manually. That matters because research languages often fail at the first install step; a package keeps the barrier low.

Modes d'utilisation

Users install Koka to compile and experiment with `.kk` programs, run examples from the language book, explore effect handlers, and test language-design ideas around typed effects and memory management. The command-line compiler is the main package surface.

Because the documentation explicitly notes missing package management and limited async libraries, Koka is best understood as a language lab and compiler package rather than a general-purpose runtime ecosystem comparable to Go, Rust, Python, or Haskell.

Pourquoi les passionnés de paquets s'y intéressent

Koka is the kind of package that makes language-runtime sections interesting: it exposes active programming-language research through a normal package manager. Its presence beside production compilers lets users compare how ideas such as algebraic effects and handlers move from papers into runnable tools.

It also shows the long tail of package indexes. Not every compiler package is there for production deployment; some are there because a reproducible install is the difference between reading a paper and trying the idea.

Chronologie

• 2012-04-13: Microsoft Research records the Koka project as established.
• 2014: Daan Leijen published work on Koka and row-polymorphic effect types.
• 2021-08-23: The Koka book notes ICFP 2021 work on generalized evidence passing for effect handlers.
• 2024-01-13: GitHub release metadata records Koka v3.0.0.
• 2026-03-17: The Koka book dated 2026-03-17 documents Koka v3.2.3.

Related projects

• Koka belongs near research and functional languages such as Haskell, OCaml, Eff, Links, and Multicore OCaml discussions of algebraic effects. Its implementation work also relates to compiler research on reference counting, effect-handler compilation, and typed intermediate representations.

Sources

• https://api.github.com/repos/koka-lang/koka/releases
• https://arxiv.org/pdf/1406.2061
• https://koka-lang.github.io/koka/doc/book.html
• https://www.microsoft.com/en-us/research/project/koka/
• https://www.microsoft.com/en-us/research/publication/first-class-named-effect-handlers/