This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-18
Channels
- # admin-announcements (3)
- # announcements (7)
- # aws (1)
- # beginners (76)
- # boot (340)
- # cider (9)
- # clara (35)
- # cljs-dev (7)
- # cljsjs (16)
- # cljsrn (11)
- # clojars (1)
- # clojure (192)
- # clojure-dev (6)
- # clojure-madison (8)
- # clojure-russia (373)
- # clojurebridge (1)
- # clojured (9)
- # clojurescript (172)
- # community-development (1)
- # core-async (2)
- # cursive (7)
- # data-science (2)
- # datomic (12)
- # devcards (1)
- # dirac (63)
- # emacs (3)
- # events (10)
- # gsoc (3)
- # hoplon (1)
- # jobs (1)
- # juxt (20)
- # ldnclj (4)
- # lein-figwheel (12)
- # leiningen (1)
- # off-topic (21)
- # om (232)
- # onyx (64)
- # parinfer (8)
- # proton (21)
- # re-frame (8)
- # reagent (1)
- # ring (3)
- # ring-swagger (3)
- # slack-help (4)
- # spacemacs (6)
- # testing (3)
@darwin: apologies for my tardy response: regarding devtools sources. I'm just confirming on latest Chrome unstable v50.0.2652.0 dev (64-bit) on Ubutnu 14.04 Dirac devtools does NOT show cljs, only js and normal devtools does. I have not tried release Chrome but will report when I get a chance.
as for the issue on go channel debugging, that would be really awesome. I had been thinking how cool it would be to have go consumers and producers as nodes and channels as edges in a graph
I’m a bit worried to keep it up to date with devtools evolution, the official devtools moves quite fast
I wondered if you need to fork the core-async though, couldn't a bootstrapped compiler work as well for this kind of tools?
core.async would need to keep track of all channels and go blocks, so I could expose it in the UI
well I thought you'd build an index of all occurences of puts takes and channels and then put them in a proxy channel to tunnel them so you can inpect the values
I can imagine some library on top of core.async, which would track that information and then expose it in some form for debugging
but it is hard to imagine some analyser for general clojure(script) code using core.async without changes
in that library you would need primitives for connecting channels, basically building that graph via some kind of api
in my issue, I had in mind more low level view of core.async. it would just list pending go blocks and state of all existing channels
any idea what could be wrong with "Use of undeclared Var projectname.core/variable at line 1 <dirac repl>" ?
this is standard REPL behaviour, it does not know about your vars until you require the namespace (aka eval it in the context of REPL)
if you don’t have evaluated the code, it warns you, but it compiles down to correct matching js just by coincidence
if I do it in a figwheel repl I don't need to, but that might already have required it or so
the only other thing I've run in to so far is no having the same focus behaviour as regular dev tools. Sometimes input loses focus and I need to manually click the input line (which is really small for some reason in canary, might be my high dpi setting.)
in next version I would like to describe how to bind a global system keyboard shortcut to focus dirac prompt
I try to not use the mouse at all, and the devtools are pretty bad for that. It took me a long time to find out that if you detach the dock you can tab between the page and devtools.