This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-20
Channels
- # announcements (1)
- # babashka (4)
- # beginners (8)
- # cider (4)
- # clj-kondo (10)
- # cljdoc (1)
- # cljsrn (7)
- # clojure (3)
- # clojure-europe (20)
- # clojure-france (3)
- # clojure-sg (2)
- # clojurescript (16)
- # clojureverse-ops (3)
- # community-development (5)
- # core-async (35)
- # cursive (1)
- # datahike (14)
- # datomic (7)
- # events (5)
- # fulcro (59)
- # graphql (11)
- # lsp (33)
- # meander (1)
- # off-topic (33)
- # polylith (23)
- # portal (33)
- # re-frame (1)
- # reagent (10)
- # reclojure (7)
- # reveal (14)
@whilo It seems the datalog parser in clj-kondo doesn't understand symbols in the query:
'[:find ?arity
:where
[?x :call/arity ?arity]
[?x :var/name assoc]
[?x :var/ns clojure.core]]
Hi Michiel, thanks for reporting. Should I https://github.com/lambdaforge/datalog-parser/issues/new? I've worked on the datalog-parser once. Probably I can investigate that soonish...
It seems to me symbols are allowed as data in Datomic. As i write in a later post in this channel this works in Datomic:
(q
'[:where [?e :s plain]
:find ?e]
'[[1 :s plain]])
I think it’s because constants are any non-variable data literal
Source vars can also be data
(q
'[:where [?e :s $plain]
:find ?e]
'[[1 :s $plain]])
Yes. I’ll see if I can fix it in datascript first.
No. But it seems the io.lambdaforge/datalog-parser
is factored out of datascript at a certain point.
Looking forward to a contribution @U021UJJ3CQ6. Happy to help if you need anything.