Clojurians Log v2

Suppose someone were to disregard your advice and try to use typed clojure now - what sort of problems would you expect them to run into?

The macro rules API is internal and undocumented. Working on an user-facing API. That makes using complex macros a little difficult, but the pieces are technically there (e.g., let and doseq are macro rules and share destructuring logic). The golden path is not very clear since there is limited tooling support and lots of backwards compatible code. the typed.clojure namespace is supposed to replace clojure.core.typed but some things haven't been ported over yet so you might end up using both (tho most of the clojure.core.typed stuff I'd discourage). The usual problems with having to annotate every var you use. Maybe LLM's could help here tbd. The usual issues with precision, trying to figure out if you're using the type system wrong vs the type system isn't precise enough. Documentation.

I have pretty comprehensive LLM-generated reference documentation in a private branch that I need to review and add automated tests. It will help a lot. The most up-to-date documentation is here https://github.com/typedclojure/typedclojure/tree/main/website but it's mostly higher level philosophical stuff.

Problems you won't run into: erasing typed clojure in production, having typed clojure change your code's semantics.

It's still being developed but I recommend clj-kondo/malli/schema/spec for now.

My PhD dissertation addressed some of the pain points, in particular by adding macro rules, symbolic execution, and tooling to infer types from code (now entirely replaced by tooling to convert malli to types).

I've been slowly adding more ideas from my dissertation to the actual implementation. The latest architectural change that would be new to you is the type checking procedure is parallelized by top-level form using a work-stealing thread pool. Code is eval'ed up front then macroexpansion/checking is done in a second pass in parallel. Next step is to cache the results for forms/files.

I'd say just use clj-kondo + malli and keep an eye on how things develop here and there should eventually be a good user story for getting type checking up and running quickly from there.

Thanks for all the info!