[CLJS-748] Dump analyzer state during a compilation. Created: 13/Jan/14 Updated: 03/Jan/15 Resolved: 03/Jan/15
CLJS doesn't have the luxury of a fully-reified runtime environment, therefore effective tooling needs a view of the internal compiler state. This issue addresses this need by enabling a dump of the compiler state based on additional cljs compiler options.
The compiler state is a map contained within an atom, either passed in as the 'compiler-env' arg to cljs.closure/build or contained globally within cljs.env/compiler.
The prototype is implemented as such:
|Comment by Gary Trakhman [ 13/Jan/14 6:46 PM ]|
Added implementing patch
|Comment by David Nolen [ 16/Jan/14 5:21 PM ]|
I question the utility of :dump-analysis-full for now. Lets remove it.
|Comment by Gary Trakhman [ 16/Jan/14 5:32 PM ]|
I was thinking it might be good along with :print followed by a pipe, but... I don't have an explicit use-case. I'll create a new patch.
|Comment by David Nolen [ 03/Jan/15 6:13 PM ]|
This ticket is subsumed by :cache-analysis support