This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-30
Channels
- # announcements (40)
- # babashka (41)
- # beginners (32)
- # calva (15)
- # clara (8)
- # clj-kondo (14)
- # cljs-dev (30)
- # clojure (37)
- # clojure-dev (8)
- # clojure-europe (21)
- # clojure-norway (21)
- # clojure-uk (4)
- # clojured (3)
- # clojurescript (4)
- # community-development (10)
- # core-async (13)
- # cursive (23)
- # datomic (15)
- # emacs (9)
- # fulcro (3)
- # google-cloud (4)
- # graphql (24)
- # gratitude (2)
- # holy-lambda (4)
- # honeysql (5)
- # hyperfiddle (9)
- # keechma (1)
- # klipse (5)
- # lsp (23)
- # malli (4)
- # missionary (32)
- # pathom (28)
- # re-frame (2)
- # reagent (40)
- # reitit (17)
- # releases (2)
- # remote-jobs (1)
- # shadow-cljs (25)
- # specter (3)
- # vim (19)
- # xtdb (41)
Can I add a JIRA issue based off the suggestion from @hiredman on https://ask.clojure.org/index.php/12012/auto-gensym-in-recursive-macros or should I wait until/if someone from the core team replies?
Yeah seems so. I think an example illustrating the behaviour on clojuredocs may suffice. Cheers
To put more nuance on this, I think we would be more likely to address it if it was actively causing issues.
Thanks @U050WRF8X - it's actively caused me an issue once, and I rectified it pretty easily, so I doubt that counts for much 😄. I updated the clojuredocs page so hopefully that'll be enough to help those who encounter this in the future.
Thank you for taking the time to think about this and for sharing your understanding on clojuredocs!