@dnolen what are you current plans for using cljs.spec/fdefs for cljs internals? ie. (defn x :foo) throws a clojure.core.specs related error vs a {:tag :cljs/analysis-error ...} in CLJS

currently looking into how I could possible leverage spec for the above tool stuff

any plans to create something like clojure.core.specs for CLJS? maybe even use some of them?

assuming we are waiting for things to finalize for CLJ first

@thheller happy to take a patch that either uses what Clojure has or copies them over

ok cool, will look into that

@thheller FWIW there's a ticket for that already http://dev.clojure.org/jira/browse/CLJS-1813

@anmonteiro good to know, thx

@anmonteiro @mfikes have you ever noticed the following in self-host (happening in planck and lumo) ?

cljs.user=> `(require 'speed-of-light.test-runner)
(cljs.core/require (quote speed-of-light/test-runner))

note the slash

(happening in replumb too)

Perhaps a bug in the compiler

weird

will open a Jira

http://dev.clojure.org/jira/browse/CLJS-1982

@dnolen can you tell me the reason why (def x foo) only emits a warning for CLJS but is a hard error in CLJ? I know that I can add a warning handler to turn it into an error, just trying to figure out why this behavior is different to clojure?

assuming foo is undeclared of course

it doesn’t matter why it’s different now

it just is and we’re not going to change it

don't mean to change it ... just curious if there is a reason I might be missing

I don’t recall that behavior is almost 5 years old

JS being more dynamic and all

you can probably crawl through the git history to figure it out, but I really don’t remember

ok thx

I suspect since we generate source files

if we errored then we’d have to clean up

in general though the philosophy has been if the issue doesn’t need to stop the compiler we just warn

this over following Clojure’s behavior closely

yeah CLJ probably can't continue in this case, JS doesn't really care

I'm just still trying to find the best strategy for the error reporting thing I posted yesterday

CLJS is so much nicer to work with because of the rich metadata we have

{:file "demo/warnings.cljs", :line 3, :column 1, :end-line 3, :end-column 13}

CLJ I get :line and :column when I'm lucky 😛

heh yeah

the whole reason for tools.reader was to get line/column without waiting for Clojure

impossible to do source maps without good info

yeah, warnings are also a lot better since they contain very useful things

CLJ just throws very bare exceptions with minimal info

yep, another place we could just do more

yeah I just threw together a little hack to get the form that caused the warning into the warning

as its not always in there

happy to take patches that make it more consistent

yeah will do if I have something concrete ... all just experimental for now

cool