This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-01
Channels
- # aleph (3)
- # announcements (10)
- # babashka (6)
- # bangalore-clj (4)
- # beginners (91)
- # biff (7)
- # cider (25)
- # cljs-dev (1)
- # clojure (109)
- # clojure-europe (9)
- # clojure-norway (5)
- # clojure-uk (1)
- # clojurescript (22)
- # cursive (22)
- # data-science (1)
- # datalevin (5)
- # datomic (7)
- # emacs (7)
- # etaoin (1)
- # events (3)
- # graphql (12)
- # hyperfiddle (1)
- # inf-clojure (1)
- # lsp (69)
- # luminus (1)
- # meander (21)
- # nbb (4)
- # off-topic (27)
- # other-languages (12)
- # rdf (58)
- # releases (3)
- # remote-jobs (2)
- # rum (12)
- # shadow-cljs (4)
- # sql (3)
- # xtdb (1)
If someone has quoting problems in cmd.exe or bash or whatever other shell, you can also launch a clojure from #babashka REPL:
user=> (babashka.tasks/clojure "-X clojure.core/prn" {:x "foo"})
{:x "foo"}
user=> (babashka.tasks/clojure "-X clojure.core/prn" {:x 'foo})
{:x foo}
🆒 5
💪 2
I've noticed there are issues when aliasing another namespace that shadows the current namespace's name, and using a protocol. Not sure if this is a known thing, I could open an issue if you'd like.
(ns x
#_(:require [clojure.pprint :as x])
)
;;; when the alias is used I get
;; Type: clojure.lang.ExceptionInfo
;; Message: Could not resolve symbol: x/IProto
;; Phase: analysis
(defprotocol IProto
(proto-method [this]))
(version v0.9.161)