This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-18
Channels
- # aws (21)
- # babashka (32)
- # babashka-sci-dev (3)
- # beginners (17)
- # biff (1)
- # calva (8)
- # clj-kondo (1)
- # cljfx (8)
- # cljs-dev (3)
- # clojure (13)
- # clojure-belgium (1)
- # clojure-europe (16)
- # clojure-losangeles (2)
- # clojure-norway (6)
- # clojurescript (11)
- # conjure (1)
- # data-science (1)
- # fulcro (2)
- # gratitude (5)
- # helix (1)
- # joyride (3)
- # malli (14)
- # nbb (4)
- # off-topic (11)
- # other-languages (10)
- # polylith (4)
- # re-frame (2)
- # sci (3)
- # shadow-cljs (20)
- # spacemacs (3)
- # tools-deps (1)
- # vim (4)
Hi community! I’m just checking if anyone has any ideas about the problem that interface
is a reserved word in ClojureScript. @imre and I have two different ideas that we have discussed in https://github.com/polyfy/polylith/issues/187. I’m not sure which one is the best, but I’m interesting to hear if you think you have a better idea (e.g. by making ifc
or interface-
the default) or what you think about the two suggested solutions.
Its a shame interface is reserved, I like the idea of a descriptive term, could we perhaps come up with something else that's not loaded, I started using ensemble
but I wonder about something like exposed
, I think a single override instead of a vector seems like a good decision as it keeps things consistent, but I feel like new projects should set a word that work for clojurescript by default, so new projects would have the keyword set but if its unset it falls back to interface perhaps.
those are my thought on the subject anyway if that helps.