deprecated-coalton-prototype
mun
deprecated-coalton-prototype | mun | |
---|---|---|
9 | 26 | |
216 | 1,752 | |
- | 0.9% | |
1.4 | 7.3 | |
over 2 years ago | 18 days ago | |
Common Lisp | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
deprecated-coalton-prototype
-
The thing is, if you start with Common Lisp, it's pretty easy to write a DSL that adds the constraints and provides the guarantees that you need. [..] Maybe all I had to do to turn CL into Haskell is implement the Hindley-Milner algorithm.
can't jerk
-
Hell Is Other REPLs
I used to use CL quite a bit, but have since abandoned it for Haskell, so I'm a bit biased.
There's a number of issues with that:
- I'd be missing all the optimizations that can be performed due to purity.
- There's more to Haskell's type system than just vanilla Hindley-Milner, and the implementation of it isn't particularly trivial. https://github.com/stylewarning/coalton is the closest thing and it's still missing a large amount of the type system.
- Doing the implementation would be a significant amount of work to get it to integrate well with the language, and it would be a layer tightly glued on top instead of integrated with the language.
- A major part of Haskell is the standard library, a good chunk of the semantics of Haskell people use on a day to day basis, like monads and etc, are a part of the standard library.
-
Six years of professional Clojure development
This looks like something Common Lisp does better, however I have too little Clojure experience to compare. CL (and SBCL in particular) does "good enough" static type checks, it throws warning at compile time (when we compile one function with a keystroke). We can also precise our function types gradually. It isn't a HM type system (Coalton[1] could be it) but it's already great (compared to no compile-time types at all).
Oh, about interactive development: that's sure, CL shines here. Objects get updated (lazily) after a class change, we can install Quicklisp libraries without restarting the image, etc. It's very smooth.
1: https://github.com/stylewarning/coalton
- Common lisp or Racket as a first lisp?
- Coalton is a dialect of ML embedded in Common Lisp
- Coalton – a dialect of ML embedded in Common Lisp
-
What would you like to see in a CL dev environment?
Help out with Coalton.
-
Stupid protocols for CL - Is this a bad idea?
If you like this kind of stuff, maybe you can help implement type classes in Coalton.
-
On repl-driven programming
(there's a work-in-progress library to add a dialect of ML on top of CL: coalton)
mun
-
Hotswapping on native languages?
Mun is a statically typed language that compiles to machine code with LLVM, designed to be hot-reloadable: https://mun-lang.org/.
-
Best language to use as a scripting lang for my rust app
Perhaps https://mun-lang.org? Might be a bit raw for your needs tho.
-
Mun v0.4.0 released
But that’s not all! In total, this release contains 111 pull requests made by 5 of our community contributors and our two Core Team members & Dependabot. Thanks for having our back! For a full list have a look at the changelog, but the main improvements are:
-
Mun v0.4.0: a statically-typed scripting language like Rust, written in Rust
Whenever I read about Mun, I'm always really, really intrigued… Until I remember that it currently has no string type and support for one is not currently planned. That's a bit of a shame, IMHO, because otherwise, this looks great!
-
Wren is a small, fast, class-based concurrent scripting language
There's mun [1] which is statically typed and AOT compiled.
1: https://github.com/mun-lang/mun
-
Lessons from Writing a Compiler
From the reverse-dependencies of the salsa crate, the (archived) Lark compiler used it and the Mun compiler uses it.
-
(async) Rust doesn't have to be hard
I notice that there are projects like mun trying to achieve a similar goal, but I'm kind of curious why they are not getting much attention from the community.
-
Rust Is Hard, Or: The Misery of Mainstream Programming
Have you heard of https://mun-lang.org/ ?
It's an embeddable scripting language with the goal of being a Rust-like language that supports hot reloading of functions AND data. To achieve the latter, it uses GC'ed memory such that memory can easily be mapped when the memory's type changes.
It's still in early development but maybe one day will serve your needs :)
-
After working on our Godot + Rust game fulltime for one year it is now up on Steam
In terms of pure Rust engines/frameworks it seems the overall "problem" is lack of scripting, at least from my perspective. Mun seemed extremely interesting, but since even the project itself says "don't use it" I guess it's not a real option, and considering the amount of time we spent on the GDScript/Rust integration I'm a little worried that rolling something more custom would be even less efficient.
- Python interpreter written in rust reaches 10000 commits
What are some alternatives?
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
Rhai - Rhai - An embedded scripting language for Rust.
immer - Postmodern immutable and persistent data structures for C++ — value semantics at scale
rune - An embeddable dynamic programming language for Rust.
yale-haskell - HASKELL: Yale Haskell system written in Lisp
janet - A dynamic language and bytecode vm
kandria - A post-apocalyptic actionRPG. Now on Steam!
lobster - The Lobster Programming Language
clj-kondo - Static analyzer and linter for Clojure code that sparks joy
RustPython - A Python Interpreter written in Rust
austral - Systems language with linear types and capability-based security.
tl - The compiler for Teal, a typed dialect of Lua