This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-20
Channels
- # announcements (8)
- # babashka (19)
- # beginners (100)
- # boot (3)
- # calva (16)
- # cider (8)
- # cljdoc (6)
- # cljsrn (15)
- # clojure (73)
- # clojure-europe (7)
- # clojure-france (1)
- # clojure-italy (12)
- # clojure-nl (11)
- # clojure-sg (1)
- # clojure-uk (17)
- # clojurescript (63)
- # cursive (22)
- # data-science (2)
- # datomic (2)
- # defnpodcast (1)
- # docs (1)
- # fulcro (7)
- # graalvm (8)
- # jackdaw (1)
- # kaocha (11)
- # off-topic (26)
- # pedestal (4)
- # planck (1)
- # re-frame (35)
- # reitit (5)
- # ring (3)
- # shadow-cljs (25)
- # slack-help (11)
- # spacemacs (8)
- # specter (2)
- # tools-deps (61)
- # vscode (6)
- # xtdb (3)
nice about the changes to support different ns per socket :thumbsup: (that's not something that shadow-cljs does unfortunately, making multiple connections to a process less useful -- actually that's the last i checked...may be things are different now)
also appreciate the :reload
support
good to hear. thanks to @mauricio.szabo for prompting me about some issues with the socket repl
@mauricio.szabo have you asked thheller about supporting a different ns per socket?
@sogaiu not really, the issues on bb were to support changing ns on a socket repl. Commands like ns
and in-ns
were failing when connected via socket.
I kept track of the current namespace in two places which went out of sync, but now it's only one place.
@mauricio.szabo ah ok, thanks. what i found is that for 2 sockets that are each in a cljs repl, they end up always being the same ns. if you in-ns in one, the other changes too.
I'm guessing but for cljs it might be related to dynamic vars not being really dynamic vars, since there are no threads, they cannot have a thread-local binding