最近 #Coalton を使っている理由は設計を明示するためで、クリーンアーキテクチャがうまくいくのか試験するにはよい型システムがあった方が嬉しい。
(なんでそもそも #Lisp なのかというと Lisp でないと趣味で書く気にならないからというのがあり……)

#Coalton で iter:drop! が何故かなかったので自分で定義する必要が生じ、実装の方法をだらだら考えていたら時間が過ぎていた。 #qkdev

I use #passwordstore, but unfortunately, it's a bash script which doesn't work well on #windows. A good excuse to try out #coalton, which is an embedded #haskell like language for #commonlisp! Not exactly production ready quality, but good enough for me.

Coalton is a really nice pragmatic language and gives the "best of both worlds" feeling.

https://github.com/simendsjo/passish

@rml
I hope this finally turns more developers on to the benefits of static type checking with algebraic data types. There are a few other languages that do this too.

#Haskell
#OCaml
#Fsharp
#Scala
#PureScript
#Shen
#Coalton
#Hackett
#Roc

Roc is the latest entry, and it is fascinating how it can automatically translate pure code into efficient state mutations under the hood. I hope #verse turns out to be as good! https://www.roc-lang.org/

I've been looking into #coalton as a new language to learn, the way it interfaces with common #lisp seems rad.

Trying it out, I'm having some issues fitting it into my workflow. Normally in #emacs I use "eval-last-sexp" to define and call functions. Everything in coalton either has to be within "coalton-toplevel" or a "coalton" wrapper, just evaluating raw expressions gives an error.

Any ideas about how I can run Coalton code as easily as I can with regular Lisp? Maybe there's a hook I can use to automatically wrap expressions before they're sent to the REPL...

Using #coalton to implement a quantum compiler
#lisp
https://t.co/mofSJ4IxYC

I am neck deep in #lisp these days, but I miss #haskell so much 😢​ I know there is #coalton but it is not the same. I crave for the mystical feeling of 'everything will fit together because "math"' (although I don't understand jack of said math, but I try and it is fun)