claro-lang VS koka

Interesting, although it seems to currently be missing a license. While Bazel and I are for sure not friends, I found this funny https://github.com/JasonSteving99/claro-lang/blob/v0.1.495/W... I guess it's similar to having a maven build under Nix but my relationship to Bazel is why I got a chuckle out of the russian doll setup

Oh wow, it looks like we've stumbled upon the same construct! In my language, Claro, what you call "interfaces" are called "contracts". I've found it to be a very powerful abstraction!

In fact, you've actually been a huge source of inspiration for building keyword-generics into the programming language I've been working on in private for the past 2 years! The language is called "Claro" and if you're interested, please take a look at the blocking-generics syntax that your initiative has inspired.

I've tried to do something unique in my lang, Claro. To avoid spamming my same comment again, check out my answer to a very similar thread yesterday

Didn't see the Github link (but having all the info here is certainly appreciated)

Hmm, so I still feel that C3's imports actually are binding to a specific implementation like other imports (Java/C/python/etc). I think a language would need to embed dependency injection concepts deep into its veins to avoid this. You'd need a way for implementation files to specify that they depend on something with a certain name and a certain interface but not to name the specific implementation. Then a separate parallel module system (more like a Guice (dep injection framework) module than the modules in C3) would indicate the specific implementation that happens to be desired this run of the program. This is the inherent modularity that I'm looking to implement in Claro. There's some prototyping of this idea in the example programs at https://github.com/JasonSteving99/claro-lang/blob/main/src/java/com/claro/claro_programs/modules.claro

In Claro I'm trying the following distinct types of procedures:

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

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%20Extractor,with%20that%20effort.)

And https://github.com/koka-lang/koka/issues/31#issuecomment-1482200826

It also offers a great Inversion of Control mechanism where everything is customisable, and, unlike Capability Objects, AESs also offer compatibility with type inference (you can pass functions doing IO to map, and it Just Works(TM)) and first-class control over stack frames (because really a continuation function is just some stack frames, which you can manually move to the heap if you want a closure; which means async is an effect!). It also is composable in ways Monads are not.

Koka and other languages implementing Algebraic Effect Systems make everything a user-defined case of coroutines: async is just another effect/Monadic type. Zig does something similar by having first class stack frames, making all function calls possibly asynchronous.

Super interesting, there is a proposal to add this to JavaScript and several languages that use this, unison, koka & eff. I had no idea this was even a thing!

Koka, already cited in this thread, early 2010s. Koka's first claim to fame was a usable effect system (at the type were, basically, effect systems were not usable in practice; in fact few languages have managed to do as well as Koka since). Now its author is working on cool implementation strategies for functional languages as well.

I'm a software engineer with 3 years of professional experience. I worked for 2 years at Microsoft on Azure Compute and now work at Google, working on improving Google search. I am the sole maintainer of the popular open-source library microlens with 80k downloads. I've also contributed to the Koka programming language developed at Microsoft Research.

By implementing all of those optimizations in the Koka programming language, they achieved GC overhead much less and execution time faster than the other languages including OCaml, Haskell, and even C++ in several algorithms and data structures that frequently keep common sub-structures of them, such as red-black trees. For more information, see the latest version of the paper.