This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-05
Channels
- # announcements (5)
- # beginners (49)
- # boot (9)
- # calva (34)
- # cider (9)
- # clara (18)
- # clj-kondo (1)
- # cljsrn (7)
- # clojure (196)
- # clojure-dev (4)
- # clojure-europe (11)
- # clojure-france (3)
- # clojure-nl (13)
- # clojure-norway (2)
- # clojure-spec (8)
- # clojure-uk (85)
- # clojurescript (87)
- # clojurex (202)
- # core-logic (6)
- # data-science (6)
- # datomic (9)
- # dirac (1)
- # duct (93)
- # emacs (9)
- # events (1)
- # fulcro (22)
- # hoplon (30)
- # jackdaw (10)
- # keechma (1)
- # leiningen (5)
- # malli (17)
- # off-topic (9)
- # other-languages (3)
- # pedestal (7)
- # re-frame (3)
- # reagent (5)
- # reitit (9)
- # remote-jobs (6)
- # rewrite-clj (80)
- # ring (2)
- # shadow-cljs (191)
- # tools-deps (54)
- # vim (14)
- # xtdb (7)
after some reconsideration and spelunking...@seancorfield i noticed you have made some commits to core.logic in the past, perhaps you would know what a good way to report about the project.clj issue mentioned above is.
My commits have been purely administrative -- I haven't touched the code and I've never used core.logic
.
According to https://clojure.org/community/contrib_libs core.logic
is "Stable" -- meaning development is irregular at best.
If you have a JIRA account, you can log an issue here https://clojure.atlassian.net/projects/LOGIC/issues
Otherwise, write up an issue on http://ask.clojure.org and Alex should see it and if it's just a matter of updating project.clj
or the instructions, he may go ahead and do it @sogaiu
@seancorfield thanks for the help!