This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-27
Channels
- # bangalore-clj (1)
- # beginners (27)
- # boot (16)
- # cider (14)
- # cljs-dev (94)
- # cljsrn (8)
- # clojure (229)
- # clojure-dev (5)
- # clojure-dusseldorf (6)
- # clojure-italy (8)
- # clojure-norway (8)
- # clojure-russia (22)
- # clojure-sanfrancisco (2)
- # clojure-spec (48)
- # clojure-uk (44)
- # clojurescript (47)
- # core-async (87)
- # cursive (43)
- # datascript (22)
- # datomic (20)
- # defnpodcast (5)
- # emacs (6)
- # hoplon (4)
- # jobs-rus (4)
- # keechma (2)
- # klipse (8)
- # leiningen (2)
- # luminus (2)
- # lumo (14)
- # om (38)
- # onyx (4)
- # overtone (3)
- # pedestal (41)
- # planck (72)
- # powderkeg (42)
- # proton (46)
- # protorepl (9)
- # reagent (9)
- # ring (47)
- # ring-swagger (5)
- # rum (7)
- # sql (22)
- # unrepl (1)
- # untangled (24)
- # vim (19)
- # yada (5)
How do you feel about adding asynchronous counterparts to the synchronous file operations?
I've been thinking more about the point of threading in the nREPL server, and I believe the reason there's no async i/o is because you just wrap things in thread or future calls
However, JavaScript doesn't have that ability, instead opting for callbacks and event loops
I see no issue with that. (Planck already has support for an async variant of clojure.shell
, for example.)
@achikin Have you seen http://planck-repl.org/dependencies.html ?
Works great with clojurescript.csv
but things like clojure.data.xml
or clj-http
refuse to load.
A small example is at the bottom of http://planck-repl.org/planck-namespaces.html for HTTP
@mfikes it works perfectly, but I wanted to use planck to explore several “native” libraries.
What kind of error do you get with clojure.data.xml
? (Perhaps it is not compatible with self-hosted ClojureScript.)
From the docs of clojure.data.xml
The Clojurescript implementation uses the same namespace as the Clojure one clojure.data.xml.
the docs suggest 0.0.8 as the latest stable, which doesn’t seem to contain cljc stuff.
Since you’re here @mfikes, what do you think of https://github.com/mfikes/planck/issues/466
Issue #446 seems reasonable. I bet to pull it off you'd have to convey it via a well-known JavaScript variable.
If it were exposed at the ClojureScript level, I wonder what namespace it would be in.
How’s it done with in-ns
? Because I found that lumo has lumo.repl/in-ns
whereas planck has it as in-ns
I don't understand the in-ns
question. FWIW, in-ns
is a REPL special that switches to, or creates a namespace.
Whereas in planck it doesn’t hava a ns, it seems to live at some top-level, since it’s only called by issuing in-ns
My thought was that if you had a function/var which lived in the same place as plancks in-ns
, it could be the same place for all repls.
Oh. Right. You are effectively saying *repl-capabilities*
could be a REPL special. Gotcha.
cljs.user=> (require '[planck.core :refer [resolve]])
nil
cljs.user=> (-> 'println resolve meta :arglists)
([& objs])
cljs.user=> (-> '+ resolve meta :arglists)
([] [x] [x y] [x y & more])
Ah. Interesting. With Planck, I took the approach of porting Clojure core functions by putting them in the planck.core
namespace. The planck.repl
namespace has some things that are in cljs.repl
(like source
, doc
, pst
, etc.)