This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-31
Channels
- # beginners (9)
- # boot (38)
- # cider (7)
- # cljs-dev (181)
- # cljsrn (49)
- # clojure (136)
- # clojure-italy (44)
- # clojure-losangeles (1)
- # clojure-news (1)
- # clojure-russia (3)
- # clojure-sanfrancisco (1)
- # clojure-serbia (2)
- # clojure-spec (28)
- # clojure-uk (41)
- # clojure-ukraine (1)
- # clojurescript (103)
- # core-async (6)
- # core-logic (46)
- # cursive (5)
- # data-science (8)
- # datascript (6)
- # datomic (5)
- # emacs (35)
- # events (3)
- # jobs (2)
- # jobs-rus (2)
- # juxt (6)
- # lumo (7)
- # off-topic (101)
- # om (6)
- # onyx (6)
- # parinfer (38)
- # pedestal (5)
- # perun (1)
- # planck (4)
- # protorepl (4)
- # re-frame (62)
- # reagent (20)
- # remote-jobs (1)
- # ring-swagger (1)
- # spacemacs (16)
- # unrepl (43)
- # vim (13)
Not really. Many of the examples out there outdated, and few of them are written by people who have a strong understanding of core.logic. I don’t see much new being written, since for the most part core.logic has been abandoned. Being a core.* project with JIRA and the whole clojure process behind it means it’s unlikely that it will get significant contributions
@swizzard I am currently learning it too, maybe we can discover stuff together ;) defne, as I understood it, is just a short form for defn + matche
As you’ve discovered, the reasoned schemer approach to learning core.logic isn’t great
at one point rackspace's managed security was using or planning on using core.logic, but I haven't seen them asking about it in a while so they may have changed it up
I can't imagine any of the clojure teams I've worked with letting something written in core.logic through code review. The first comment would be "this would be clearer if you used map / filter / etc"
because at the beginning what you are doing isn't so complicated, so it seems like you could just do it with map and filter and whatever, and it would be easier for people to follow
the seq library is some kind of local maxima, and it takes a bunch of energy to get to something else
I don't think a lot of teams can do it (as I've said none of the teams I've been on seemed to want to spend energy in that way)
sorry, I think I am not being clear, I 100% think core.logic is a better for a lot of cases
but it doesn't get used because programmers aren't willing to expend extra energy to escape the local maxima(the seq library) to get to something better
But if I can’t tell them practical things they can do with core.logic, I can’t criticize them much for not using it
I want to use it to write a type checker, maybe you can help? I saw the basic type checker example, and I am wondering how I can get type errors from my program instead of ()
with conde all the arms are tried in "parallel", but conda only the first arm with the first goal that succeeds will be tried
which would make sense here, I think, if the type terms unify you don't care about building up a list of errors