This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-01
Channels
- # beginners (133)
- # boot (59)
- # cider (5)
- # cljs-dev (30)
- # cljsrn (23)
- # clojure (212)
- # clojure-austin (3)
- # clojure-brasil (1)
- # clojure-chicago (5)
- # clojure-italy (10)
- # clojure-russia (5)
- # clojure-serbia (1)
- # clojure-spec (34)
- # clojure-turkiye (2)
- # clojure-uk (132)
- # clojurescript (163)
- # clojutre (1)
- # cursive (5)
- # datomic (58)
- # emacs (42)
- # events (1)
- # graphql (26)
- # hoplon (16)
- # jobs (1)
- # lumo (27)
- # numerical-computing (3)
- # off-topic (127)
- # om (9)
- # onyx (24)
- # re-frame (20)
- # reagent (20)
- # ring-swagger (14)
- # sql (19)
- # unrepl (28)
- # untangled (3)
- # vim (8)
- # yada (17)
@cgrand not really, people were interested though, several clojure peeps in the audience. There should be video at some point
there was one interesting question/use case. Say you have some complicated code, and you have some (prn ,,,)
in the middle to inspect some intermediate values
your repl/tooling can pretty format the final result of an expression and let you drill down into it etc, but these intermediate things will just be strings
could unrepl provide a way for your code to send extra values back to the repl/tooling
ah yes, I saw the logging thing, I thought it had more to do with traditional log file style logging
(timbre/log :info “a” (range))
[:echo {:from [14 1], :to [15 1]} 12]
[:started-eval {:actions {:interrupt (unrepl.repl/interrupt! :session329 12), :background (unrepl.repl/background! :session329 12)}} 12]
[:log [:info “user” #inst “2017-04-04T14:56:56.574-00:00” “a” (0 1 2 3 4 5 6 7 8 9 <#C4C63FWP5|unrepl>/... {:get (unrepl.repl/fetch :G__3948)})] 12]
[:eval nil 12]