This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-19
Channels
- # adventofcode (18)
- # announcements (1)
- # babashka (153)
- # beginners (73)
- # bristol-clojurians (4)
- # calva (1)
- # cider (6)
- # clj-kondo (38)
- # clojure (154)
- # clojure-dev (12)
- # clojure-europe (7)
- # clojure-finland (11)
- # clojure-nl (70)
- # clojure-spec (13)
- # clojure-uk (101)
- # clojuredesign-podcast (2)
- # clojurescript (15)
- # core-async (30)
- # cryogen (1)
- # cursive (5)
- # devops (1)
- # duct (4)
- # figwheel-main (1)
- # fulcro (19)
- # jobs (12)
- # kaocha (17)
- # luminus (2)
- # malli (8)
- # music (5)
- # nrepl (13)
- # off-topic (20)
- # overtone (3)
- # re-frame (7)
- # reagent (38)
- # shadow-cljs (13)
- # specter (3)
- # tools-deps (6)
- # vim (7)
For those who saw the movie Inception … I present you the Macroception - a macro defined in a macro https://github.com/clojure/spec-alpha2/commit/e4ae2603c055950a1b9e649e6fdb022e109fabaf#diff-30b3955ecb734ef29c10aa50217b5066R934
I was wondering if it was possible to use a double syntax quote .. lol
to avoid the (list
inside
well, that particular code is mostly a dupe of defop
- that was the annoying part (defcompop mostly copies it)
It's probably possible to DRY it out, but I assume that would be even worse
Great line for on defn podcast btw. @U04V5V0V4 maybe you should re-invite Alex, it's been almost 50 episodes 🙂
defcompop is speculative, may not survive
@U8MJBRSR5 it is possible, but there are some very subtle tradeoffs and I found this was easier
a smarter person than me could probably improve that code
I left a dependency on spec alpha2 in my current project even if I don’t use it yet, because I am happy to see a new git commit hash each time I update my deps to their latest version.
fyi, recent commits renamespaced, and prob going to change the project name too, which will break any dependees
@U8MJBRSR5 Did you know RSS also works with commits? https://github.com/clojure/spec-alpha2/commits/master.atom
but back to defop/defcompop - these were really interesting to work through. they do highlight the downsides of the macro-expander approach in spec (requiring macros to do composition)
if you don't care about the "language" side of specs (only about the programmatic side), that's not technically necessary anymore in spec 2 though