This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-10
Channels
- # admin-announcements (21)
- # announcements (1)
- # boot (91)
- # cider (2)
- # cljs-dev (46)
- # clojure (77)
- # clojure-berlin (1)
- # clojure-czech (2)
- # clojure-dev (22)
- # clojure-france (2)
- # clojure-india (1)
- # clojure-japan (16)
- # clojure-russia (6)
- # clojure-uk (1)
- # clojurescript (195)
- # cloxp (2)
- # cursive (15)
- # editors (6)
- # jobs (10)
- # ldnclj (18)
- # liberator (3)
- # off-topic (2)
- # onyx (24)
- # re-frame (4)
- # reagent (57)
@juhoteperi: before I forget yes, exposing the dep graph stuff is a find idea for the public api
@dnolen: Okay. I’ll create patch for that. Do you have option whether foreign-deps (or goog files) should be exposed in the graph?
@juhoteperi: I think a patch that exposes the entire dependency graph is the only one what makes sense.
how we deal with various kinds of dependencies need to remain internal otherwise people will break when things change
Cljs part of graph is already quite easy to construct using all-ns
and (proposed) ns-dependencies
Foreign-dep and closure data is available in :js-dependency-index
and I think there is no useful functions for accessing that yet
@juhoteperi: right so for the public api we should present a merged view
so I would write up the names and approach in the ticket when you have something and I can review that
i’ve tracked the doseq bug (CLJ 1400) to shadowing and munging, only affecting the :context :statement
and bootstrapped combination of a :loop
essentially inside the while loop the sequence name is munged differently, hence the step functions don’t advance
i’m a little bit stuck at this point, haven’t really figured out a good flow for debugging this (and println debugging is out the window in the emitter)
might be quicker for me to show what i’ve found to someone who understands those portions better?
@crisptrutski: println debugging can work, we split normal printing from error printing for this exact purpose
tried using cursive with the node repl, but got issues with loading cljs.js - expected window global
didn’t manage to figure out connecting to the browser repl - xpc parameter?
Cursive w/ Node.js REPL definitely works, should be simpler to if you use master thanks to a couple of recent commits
must have had a stale checkout, thanks
pretty handy!
while they are a priority, it’s nice to keep them separate from things that affect everyone
@mfikes: ah that defprotocol issue, might want to try locally with core/->
instead of ->
, if that works patch + test welcome
@mfikes what’s happening is that defmacro
does not work inline at all, ClojureScript bootstrapped just sees a function
so it’s trying to call ->
as a normal function and of course that won’t work because macros need to take 2 extra params
and the reason the ->
isn’t getting resolved in this case … because we exclude all that at the top