deprecated-coalton-prototype
schema
deprecated-coalton-prototype | schema | |
---|---|---|
9 | 9 | |
216 | 2,380 | |
- | 0.0% | |
1.4 | 0.0 | |
over 2 years ago | about 1 year ago | |
Common Lisp | Clojure | |
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)
schema
-
Tired by the dynamicism
Plumatic schema (https://github.com/plumatic/schema) , or friends I might be wrong, but I think schema might make more sense to you coming from the F# world (might be wrong)
-
Clojure from a Schemer's perspective
This one? I didn't. I hear good things about it, and it's reached a point of maturity, being widely used in production.
-
Worrying comment from HN on Building a Startup on Clojure
Uhhh spec has existed for a long time and before that, schema Nowadays we also have the excellent malli. If his codebase is full of functions where the shape of the data isn’t obvious, isn’t documented and isn’t specified in a specific/schema, that’s on him and his bad coding practices and really no different from passing data in other dynamic languages. A class by itself (without additional effort) only gives you field names.
-
Building a Startup on Clojure
I don't understand this reputation either. There are very large systems built on other Lisps. For example, Emacs has a massive amount of Elisp. Elisp is much more primitive than Clojure, and traditionally libraries don't use e.g. data schemas [1] as runtime contracts for data.
Obviously, once a system built on top of a dynamic language grows beyond certain threshold, you need to be very disciplined as there are no static types to ensure some degree of correctness.
[1] https://github.com/plumatic/schema
- Clojure needs a Rails, but not for the reason you think
-
General anxiety regarding learning Clojure and such
Try to learn a schema library early, like Malli or Prismatic Schema. Do not mistook them as "static-typing" things - it's more for data validation and coercion than "security that things will get the right typing information". The idea to learn them early is how you'll shape future code: validating all "output data" first, them using that data inside your program without "defensive programming" like checking every time if a specific value on a map is nil, etc
- Six years of professional Clojure development
-
What are some great Clojure libraries, as of 2021?
In Clojure, declarative data specifications for validation and generation are also very mainstream. Schema was first out the door, Clojure Spec is the most popular library, while malli is gaining popularity fast at the moment.
What are some alternatives?
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
malli - High-performance data-driven data specification library for Clojure/Script.
immer - Postmodern immutable and persistent data structures for C++ — value semantics at scale
clj-kondo - Static analyzer and linter for Clojure code that sparks joy
yale-haskell - HASKELL: Yale Haskell system written in Lisp
specter - Clojure(Script)'s missing piece
kandria - A post-apocalyptic actionRPG. Now on Steam!
matcher-combinators - Library for creating matcher combinator to compare nested data structures
clojure-dsl-resources - A curated list of Clojure resources for dealing with domain-specific languages.
austral - Systems language with linear types and capability-based security.
fulcro - A library for development of single-page full-stack web applications in clj/cljs