> If that is true, then it is a problem, indicative either of a widespread 
> lack of discipline among the tool makers or (more likely) a strong need for 
> some additional well-specified (and maintained!) APIs in the compiler for 
> tools to hook into. 
>

Sometimes it is just a simple bug or lack of robustness in a downstream 
tool that needs to be sorted before rushing to blame and/or burden upstream 
ClojureScript.

Take https://github.com/omcljs/ambly/issues/61 as an example. Previously 
ClojureScript 0.0-3030 would not print anything when evaluating (doc 
unknown-symbol), and with 0.0-3053 onwards it prints an empty string. This 
broke Ambly.

This doesn't really reflect a lack of discipline with APIs, but does 
illustrates the need to do downstream triage first.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.

Reply via email to