This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-20
Channels
- # announcements (1)
- # asami (2)
- # babashka (9)
- # babashka-sci-dev (33)
- # beginners (6)
- # calva (5)
- # cider (1)
- # clj-kondo (2)
- # clojure (79)
- # clojure-dev (8)
- # clojure-europe (1)
- # clojurescript (56)
- # core-logic (1)
- # datalevin (1)
- # emacs (20)
- # funcool (3)
- # holy-lambda (3)
- # honeysql (28)
- # improve-getting-started (11)
- # introduce-yourself (4)
- # lsp (21)
- # off-topic (9)
- # other-languages (5)
- # polylith (3)
- # quil (3)
- # releases (1)
- # rewrite-clj (9)
- # sql (5)
- # tools-deps (29)
- # xtdb (9)
https://www.unison-lang.org/learn/usage-topics/documentation/ Unison supports type-checked example code, inline evaluation, and https://en.wikipedia.org/wiki/Transclusion as part of its data structures for documentation (docs are themselves values in Unison programs). Seems like a world apart from code frozen in strings.
Unison is full of interesting bits. I wonder how much of this example could be done in Clojure with metadata
💡 1
https://danielgregoire.dev/posts/2021-10-15-clojure-src-test-meta/ I think the approach outlined here would dovetail nicely with using metadata for that purpose.