This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-24
Channels
- # admin-announcements (2)
- # beginners (46)
- # boot (8)
- # cider (29)
- # cljs-dev (45)
- # cljsjs (10)
- # cljsrn (13)
- # clojure (60)
- # clojure-dev (5)
- # clojure-greece (1)
- # clojure-ireland (4)
- # clojure-mexico (6)
- # clojure-poland (3)
- # clojure-quebec (3)
- # clojure-russia (8)
- # clojure-spec (89)
- # clojure-uk (70)
- # clojurescript (84)
- # cursive (4)
- # datomic (7)
- # devcards (1)
- # dirac (2)
- # emacs (11)
- # hispano (10)
- # jobs (13)
- # keechma (34)
- # lein-figwheel (4)
- # luminus (19)
- # off-topic (2)
- # om (78)
- # onyx (6)
- # parinfer (1)
- # planck (82)
- # proton (2)
- # re-frame (10)
- # reagent (23)
- # ring-swagger (5)
- # spacemacs (2)
- # specter (24)
- # spirituality-ethics (122)
- # untangled (13)
Just stumbled upon this and I assume it's well-covered from a cursory glance at the jira, but what's the position on
keyword
being able to produce keywords that the reader doesn't otherwise allow?It’s been discussed several times on the mailing lists over the years (and recently on Slack): there’s no problem with being able to programmatically produce keywords that you could not type in as literals to the reader.
Here’s Alex Miller’s response to the question from #C03S1KBA2 June 21st https://clojurians.slack.com/archives/clojure/p1466523388001331
@alexmiller: when you have a moment can you reboot hudson for https://github.com/clojure/build.ci/commit/59d964f1a698857b043720388d57b0fff05da25d ?