This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-10
Channels
- # announcements (5)
- # aws (18)
- # babashka (1)
- # beginners (81)
- # calva (7)
- # chlorine-clover (1)
- # cider (5)
- # cljs-dev (8)
- # clojure (125)
- # clojure-dev (1)
- # clojure-europe (31)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-norway (1)
- # clojure-spec (5)
- # clojure-sweden (1)
- # clojure-uk (31)
- # clojurescript (85)
- # code-reviews (1)
- # core-async (17)
- # cursive (39)
- # datomic (16)
- # emacs (1)
- # fulcro (6)
- # java (16)
- # kaocha (2)
- # luminus (4)
- # malli (2)
- # off-topic (65)
- # pathom (3)
- # re-frame (11)
- # reagent (5)
- # remote-jobs (1)
- # rum (5)
- # sci (10)
- # shadow-cljs (24)
- # spacemacs (4)
- # test-check (3)
- # tools-deps (22)
- # xtdb (15)
Alright here's a hard one. Has anyone figured out a way to evaluate "async" expressions? For example, I have load-image
which returns a channel. I'd like to take!
the value from this channel and evaluate the result, in a form like this (<! (load-image "/Users/neil/Desktop/stock-bg.jpg"))
. Of course, the problem is that Error: <! used not in (go...) block
when I cider-eval-last-sexp
.
in clj just (<!! ...
in cljs, you'll need to actually do the go block or use one of the async functions that provide a callback
When an exception is printed in the repl, it gets an overlay that makes it clickable to jump to the source of the frame. It seems broken to me as it fails to resolve a file. In cider-jump-to-locref-at-point
either cider-sync-request:ns-path
or cider-sync-request:info
is returning an empty string, which means the loc
plist is not checked for its “file”. Is this a bug in the middleware or in the elisp?