As stated earlier we're not going to deprecate any compiler settings, there may still be some scenarios where these settings are useful. That said, I think all development time tooling really needs to support :none, that is the baseline.
Related, I've gone ahead and started an "official" port of clojure.test to ClojureScript that is bundled in so that we can provide the community with basic testing functionality that works for all compiler settings out of the box. This thread has convinced me it is a significant problem felt by the community that needs a standard solution. Along the way I've made changes to ClojureScript analysis and compilation to ensure that anyone wanting to provide their own custom testing tooling will now find considerable support to make such work easier: * compiler support for :test metadata on vars * static vars - (var foo) will dump an object with metadata that corresponds to Clojure var metadata (:file, :line, :column, :arglists, :test, etc.) * ns-interns macro - will dump a ClojureScript map from symbols to vars * pure ClojureScript source map decoding - simplify rewriting JavaScript stack traces for test reporting I want to see people building off a common testing infrastructure to guarantee compatibility with all compiler options moving forward. Similarly for other tooling I'd rather see patches that make ClojureScript easier to work with rather than see tool authors work around the current limitations of the compiler and provide sub-optimal experiences to end users. David On Mon, Dec 8, 2014 at 8:52 AM, Chas Emerick <c...@cemerick.com> wrote: > > On 11/26/2014 03:29 PM, David Nolen wrote: >> >> On Wed, Nov 26, 2014 at 3:22 PM, Kyle Cordes <k...@kylecordes.com> wrote: >>> >>> I wasn’t speaking in favor of those settings, just pointing out that >>> there are various constraints. That is a problem with have a lot of settings >>> available, we end up with different tools supporting different >>> semi-overlapping subsets of the settings. >>> >>> Personally I’d be happy if all except the most useful settings were >>> removed. Maybe only :none and :advanced are actually still needed in 2014. >> >> No plans to remove anything. If tools are passing bad settings to the >> ClojureScript compiler or don't reliably support :none, I just would >> not use these tools. > > > If particular settings are considered "bad", then some kind of deprecation > warning is warranted. This would be a useful signal to everyone (toolmakers > included) that e.g. :simple is not useful anymore and :none is strictly > superior. > > A couple of tools I maintain (clojurescript.test and others) do not > currently support :none only because, at least when I last tried it, :none > required an arrangement of resources on disk that didn't match up well with > the rest of my workflow. I will take a fresh look at :none in the coming > weeks. > > I am conscious of the fact that lein-cljsbuild has by default become the > canonical compiler documentation, outside of various blog and mailing list > posts. I've just now merged a couple of pull requests that update its docs > to include mentions and examples using :none. At least until I am again > tracking ClojureScript compiler development on a regular basis, I will rely > upon community contributors to help keep lein-cljsbuild documentation > accurate and up to date. > > Best, > > - Chas > > > -- > 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 clojurescript+unsubscr...@googlegroups.com. > To post to this group, send email to clojurescript@googlegroups.com. > Visit this group at http://groups.google.com/group/clojurescript. -- 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 clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
