On Tue, Dec 30, 2014 at 10:46 PM, Thomas Heller wrote:
> What is tooling and what is CLJS? At which point does it make sense to
> address an issue in CLJS rather than a library. Given that probably no one
> will use the Node.JS REPL the way you described in your blog post other than
> for exper
On Wednesday, December 31, 2014 12:17:11 AM UTC+1, David Nolen wrote:
>
> Supporting both Node.js and the Browser has been a goal since the
> initial release. There's nothing new going on here except more &
> better.
What is tooling and what is CLJS? At which point does it make sense to address
On Tue, Dec 30, 2014 at 5:38 PM, Thomas Heller wrote:
> I believe most of it is due to the fact that everything has to go through
> cljs.closure/build. Since everything build related is hidden behind that
> function, CLJS has to do quite a lot instead of just worrying about compiling
> CLJS->JS
Hey,
First of all, huge thanks to David Nolen for all your work on ClojureScript.
TL;DR: I want to help, but I'm sort of "stuck".
With all the recent CLJS commits going into tooling related issues (cljs.test,
caching, ...) I find a lot of overlap to what I have done in shadow-build. I
either f
This is a tooling issue more than anything, you need to recompile the
namespace with the `run-tests` expression.
However, there is utility to a :recompile-dependents flag, and we
already have a JIRA ticket for this. When it is implemented it will
trigger all dependent namespaces to recompile.
Dav
This an edge case - that's dead code but the inference is correct.
I already landed a fix for this in master. There was no inference for
method invokes.
On Tue, Dec 30, 2014 at 7:13 AM, Shaun LeBron wrote:
> Seems to be the simplest case for this warning (run against master branch):
>
> (when-le
I am now getting things done with the following workaround:
1. Do as outlined in the first post
2. Don't use .pragma library. Instead, import the compiled js in main.qml:
import "main.js" as LoadCLJS
3. Now your stuff won't be in the LoadCLJS object, but in the global
environment. So instea
Seems to be the simplest case for this warning (run against master branch):
(when-let [x nil]
(+ x 100))
WARNING: cljs.core/+, all arguments must be numbers, got [clj-nil number]
instead. at line 4 src/example/core.cljs
On Tuesday, December 30, 2014 3:22:04 AM UTC-6, Andrew Mcveigh wrote:
> I
I have played with the tutorial provided here:
http://keeds.github.io/clojurescript/2014/12/19/cljs-test.html
It seems that new tests inside an existing namespace are not run when using
lein cljsbuild auto test.
Is it a bug in cljs.test?
On Wednesday, 24 December 2014 20:40:03 UTC+2, David N
It seems that new tests inside an existing namespace are not run when using
lein cljsbuild auto test.
Is it a bug in cljs.test?
On Friday, 26 December 2014 19:41:47 UTC+2, Andrew Keedle wrote:
> Yehonathan,
> Use :test-commands instead of :notify-command.
>
> See Anna Pawlicka's article:
> h
I'm also seeing this in cljs-time in both "0.0-2411" and "0.0-2511". The call
to cljs.core// can never be reached with a nil 'millis, but the compiler still
gives the warning.
WARNING: cljs.core//, all arguments must be numbers, got [#{nil clj-nil}
number] instead. at line 51 src/cljs_time/coer
11 matches
Mail list logo
