Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

help on none compilation option #43

Closed
magomimmo opened this issue Jan 26, 2014 · 4 comments
Closed

help on none compilation option #43

magomimmo opened this issue Jan 26, 2014 · 4 comments

Comments

@magomimmo
Copy link
Contributor

Hi Chas, I'm not able to make austin sample to work with the :none compilation. I did not find any information about austin non supporting it in the browser connected REPL scenario.
It seems to me that austin has the same limitations of clojurescript.test about :none option. Is it true?
Have you any clue about it?

Thanks so much.

@cemerick
Copy link
Owner

The same limitation exists for the same reason. In this case, the output of the "app" compilation needs to be loaded by the browser (instead of e.g. phantomjs in the testing case). Perhaps there's a reliable way in this case to locate and preload the goog bits before loading the compilation output — it's somewhere in out, I think? — but I wouldn't want to recommend depending on anything in out. :simple (or :whitespace, whatever) just works.

@magomimmo
Copy link
Contributor Author

thanks Chas. The limitation applies to piggieback too, isn't it?

@cemerick
Copy link
Owner

IIRC, :none can be used in REPL environments, but I honestly don't recall.

Is all of this interest in :none just re: TDD cycle time?

@magomimmo
Copy link
Contributor Author

On Jan 26, 2014, at 1:37 PM, Chas Emerick notifications@github.com wrote:

IIRC, :none can be used in REPL environments, but I honestly don't recall.

ok. I'll try myself next week.
Is all of this interest in :none just re: TDD cycle time?

mostly yes. I just read you comment on clojurescript.test. Comparing your numbers with mine it seems that my cljs-start template does something wrong, otherwise I wouldn't know how to justify the difference itself, even if I'm on an old iMac.

Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants