> REPL stuff to work.
>
> Olav
>
> On Tuesday, January 27, 2015 at 1:57:19 AM UTC+1, David Nolen wrote:
> > The only significant change is that Om now relies on the cljsjs.react
> artifact instead of the one I maintained myself. cljsjs.react has the
> benefit that usage of React
The multiple JS Context problem is pretty much the same as the multiple
class loader problem in Java.
We're not going to do anything about it in ClojureScript itself.
David
On Tue, Jan 27, 2015 at 9:01 AM, Dave Sann wrote:
> This is most likely related to
>
> https://groups.google.com/d/msg/cl
Instructions on running the built-in ClojureScript REPLs is covered here
https://github.com/clojure/clojurescript/wiki/Running-REPLs.
On Tue, Jan 27, 2015 at 8:50 AM, David Nolen wrote:
> Ah ok, yes I suspect Weasel will need updating for ClojureScript 0.0-2727
> and is likely the source
.com/darwin/flense-nw/tree/weasel-repl
>
> I don't expect more help here because this is probably an issue on Weasel
> side:
> https://github.com/tomjakubowski/weasel/issues/41 (and others)
>
> Thanks for you patience.
>
>
> On Tuesday, January 27, 2015 at 2:18:42 PM UTC
This isn't very useful without seeing the contents your project.clj or the
output of `lein deps :tree`.
This goes for everyone having trouble on this thread.
David
On Tue, Jan 27, 2015 at 7:17 AM, Antonin Hildebrand <
antonin.hildebr...@gmail.com> wrote:
> I have just double-checked my local ma
The only significant change is that Om now relies on the cljsjs.react
artifact instead of the one I maintained myself. cljsjs.react has the
benefit that usage of React with addons instead of plain React may be
configured via Maven in your pom.xml or your project.clj. It's exciting to
see that we ar
The latest released version of Om is 0.8.4 did you try this one?
David
On Mon, Jan 26, 2015 at 6:14 PM, Makoto H. wrote:
> He Antoni,
> The situation was the same after remove cemerick.piggieback/wrap-cljs-repl.
> I did another test.
>
> I checked differences between om 0.8.1 and 0.8.2.
>
> In
Nice!
On Mon, Jan 26, 2015 at 9:02 AM, Martin Klepsch <
martinklep...@googlemail.com> wrote:
> CLJSJS is an effort to package Javascript libraries for use in
> Clojurescript projects.
>
> With the latest Clojurescript improvements around :foreign-libs it has
> been a pleasure to migrate all CLJSJ
On Mon, Jan 26, 2015 at 3:08 AM, Laurent PETIT
wrote:
> Yet ?
Right if Webjars was open to including the necessary information that would
be great. I suspect this will be challenging since Webjars has chosen
RequireJS as the runtime loading mechanism whereas deps.cljs provides
Google Closure ru
bower/npm/node etc.
>
> On Sunday, January 25, 2015 at 2:42:54 PM UTC-5, David Nolen wrote:
>>
>> I strongly recommend the Clojure(Script) community join forces when
>> packaging libraries to avoid duplicated effort and dependency conflicts.
>>
>> CLJSJS seems
On Sun, Jan 25, 2015 at 5:40 PM, Vladimir Bokov
wrote:
> I saw this initiative, but I hardly imagine a Github repo/organisation
> managing the whole infrastructure. As you said: we have clojars and maven.
>
For the most popular libraries having a curated set is going to be
important - Maven knob
:
> Thanks David!
>
> I also already packaged https://github.com/razum2um/jquery-cljs using
> your react repo as example
>
> суббота, 24 января 2015 г., 21:10:29 UTC+6 пользователь David Nolen
> написал:
>
>> ClojureScript, the Clojure compiler that emits JavaScript source code
It does not automatically do this but I generally try to keep it up to date.
David
On Sun, Jan 25, 2015 at 3:20 AM, Kashyap CK wrote:
> Hi,
>
> I find using mies conveniest. Does it bring be the latest and greatest
> Clojurescritpt though?
>
> Regards,
> Kashyap
>
> --
> Note that posts from ne
(defn app-view []
> [:did.sample ])
>
> (reagent/render-component [app-view] (.getElementById js/document "app"))
>
>
>
> On Sun, Jan 25, 2015 at 6:25 AM, David Nolen
> wrote:
>
>> The :source-map option is in the project.clj he pasted.
>>
>> Marc
t works (ie re-renders) anyway. What
> makes Om re-render the view after I call d/transact! on the database that I
> pass in as the root state?
>
> Stephan
>
> On Sunday, January 25, 2015 at 3:51:55 PM UTC+1, David Nolen wrote:
> > You have not implemented ICursor. Just implem
; implementing ICursor instead of IToCursor, but none of the methods were
> ever called.
>
> So how can I have a wrapper of a DataScript database that supports
> IAssociative and still make Om re-render after any change to it? What's
> missing?
>
> Stephan
>
>
> On Sun
This won't be considered a cursor since it does not implement ICursor.
David
On Sun, Jan 25, 2015 at 5:09 AM, stephanos wrote:
> Hey there,
>
> I'm trying to integrate Om and DataScript.
>
> At first I used David Nolen's gist [1] that implements 'om/IToCursor' for
> DataScript's DB type. That w
On Sun, Jan 25, 2015 at 2:49 AM, Makoto H. wrote:
> [org.clojure/clojurescript "0.0-2727" :scope "provided"]
You need to drop :scope "provided". Sounds like you're probably not getting
the version of the compiler you need.
David
--
Note that posts from new members are moderated - please be p
x27;s
> > Closure's job? Or how does the line get added? We're definitely not
> sending
> > an X header for source maps, so we must have that special comment
> > (according to what I read)
> >
> > What am I missing here?
> >
> >
> > On Sat, Jan 24,
, David Nolen wrote:
> And just cut 0.0-2725 to address a Node.js target support regression.
>
> David
>
> On Sat, Jan 24, 2015 at 10:10 AM, David Nolen
> wrote:
>
>> ClojureScript, the Clojure compiler that emits JavaScript source code.
>>
>> README and
Are you sure the source maps are accessible to the browser? You should see
them getting loaded in the Network tab.
David
On Sat, Jan 24, 2015 at 7:20 PM, Marc Fawzi wrote:
>
> at work, we've implemented a few features/pages in cljs without source map
> support.. to me that's like using the forc
And just cut 0.0-2725 to address a Node.js target support regression.
David
On Sat, Jan 24, 2015 at 10:10 AM, David Nolen
wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New
t-dir "out"
:optimizations :none
:source-map true}
Then your markup just needs:
Same as :advanced.
David
On Sat, Jan 24, 2015 at 10:10 AM, David Nolen
wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://git
Some further explanation on packaging JavaScript libraries for
ClojureScript consumption
https://github.com/clojure/clojurescript/wiki/Foreign-Dependencies
On Sat, Jan 24, 2015 at 10:10 AM, David Nolen
wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
&g
The dependency information has changed:
[org.omcljs/om "0.8.2"]
The release depends on ClojureScript 0.0-2719 as it leverages the new
foreign dependency functionality to simplify development and production
builds.
Feedback welcome!
https://github.com/swannodette/om
David
--
Note that posts f
On Sat, Jan 24, 2015 at 11:01 AM, Khalid Jebbari
wrote:
> A question (maybe stupid/obvious) : why do you need to declare the "min"
> version of js lib ? The normal version + the extern file is all that's
> needed to compress the file with the Closure Compiler, no ?
>
Declaring the minified versi
On Sat, Jan 24, 2015 at 10:43 AM, Martin Klepsch <
martinklep...@googlemail.com> wrote:
> A general question/concern I'd like to voice in that context is that
> this change makes it hard to split JS preamble from our compiled
> Clojurescript. Given that the Clojurescript code might change on a
>
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2719
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2719"]
ClojureScript is not an island, like Clojure on the
Check your dependencies. Make sure some other dep isn't bringing in a stale
version of Om. You can do this with `lein deps :tree` at the command line.
David
On Wed, Jan 21, 2015 at 12:08 AM, Mark Stang wrote:
> I am getting these WARNINGs wherever I use them:
>
> WARNING: Use of undeclared Var
ClojureScript applications start around 20k gzipped and go up from there.
In my experience for non-trivial applications that in JS would require
jQuery (30k), Underscore (5k) + MVC flavor of the day (10k) - ClojureScript
is competitive.
On Friday, January 16, 2015, Colin Kahn wrote:
> What is th
fer
>
> Den onsdagen den 31:e december 2014 kl. 21:23:02 UTC+1 skrev David Nolen:
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to cloj...@googlegroups.com
> Note that posts from new
To be clear Google Closure gives us support back to IE6 out of the box.
ClojureScript doesn't gain anything at all by dropping support for these
targets because the cost of supporting them is effectively zero anyway and
dropping them doesn't allow us to do anything new.
David
On Tue, Jan 13, 201
That's the reason. To have a calling convention that works for non-native
function types.
David
On Tue, Jan 13, 2015 at 3:42 PM, Angel Java Lopez
wrote:
> When ClojureScript finds a list like
>
> (ns myns.core)
> ;
> (myfun arg1)
>
> It is compiled to
>
> myns.core.myfun.call(null, arg1
On Tue, Jan 13, 2015 at 3:37 PM, gvim wrote:
> I was thinking more about the NodeJS platform. IO.js are supposed to be
> releasing a fork today which moves faster with V8 improvements and Joyent
> are now trying to bring them back into the fold. It may be all about
> governance really but it look
For what measurable benefit?
On Tue, Jan 13, 2015 at 3:38 PM, Angel Java Lopez
wrote:
> Umm I could see (let [x ...] compiled to ES 6 lets ;-)
>
> On Tue, Jan 13, 2015 at 5:37 PM, gvim wrote:
>
>> On 13/01/2015 17:56, David Nolen wrote:
>>
>>> There&#
suppose this is meant specifically for David Nolen. What direction will
> Clojurescript take when ES6 Harmony becomes established? Compilation flags
> for ES5 and ES6? What does ES6 offer which could improve Clojurescript?
>
> gvim
>
> --
> Note that posts from new members a
Yes the point is that #2 is a separate interesting discussion on its own
right.
But I only want feedback about how to compute modules.
On Sunday, January 11, 2015, Mike Haney wrote:
> So just to be clear, this is a compiler change only? There are no
> proposed changes to namespace loading, i.e
ly
> goog.module.ModuleLoader and goog.module.ModuleManager in the reference,
> but I find references alone difficult to use to figure out how to actually
> use something.
> It looks like this should enable #2, but I don't know how to actually do
> it.
>
> On Mon, 12 Jan
> On Sunday, January 11, 2015 at 7:11:24 PM UTC-5, David Nolen wrote:
> > Use goog.dom.classes
> >
> >
> http://docs.closure-library.googlecode.com/git-history/b75212a4258f8190d08fd518e16efe764d9d/closure_goog_dom_classes.js.html
> >
> >
> > goog.dom.c
2 is out of scope wrt. compiler support. But as far as I know this is
something that should be solvable on your own with Closure Modules.
On Sunday, January 11, 2015, Mike Haney wrote:
> There are 2 use cases I would like to see supported by this:
>
> 1) generating multiple apps from the same co
Use goog.dom.classes
http://docs.closure-library.googlecode.com/git-history/b75212a4258f8190d08fd518e16efe764d9d/closure_goog_dom_classes.js.html
goog.dom.classes.toggle with a CSS display none class should get the job
done.
That or you can use goog.dom.style
goog.dom.style.setStyle(el, "di
Currently looking into supporting Google Closure Modules. They allow
breaking up advanced compiled builds so everything need not be loaded all
at once. This would help a lot with load latency in larger ClojureScript
applications.
A basic sketch underway here:
https://gist.github.com/swannodette/0
OK, but you have not explained what exactly is not working for each of them?
David
On Sun, Jan 11, 2015 at 11:27 AM, Jonathon McKitrick
wrote:
> Here's one set
>
> :cljsbuild {:builds
> {:prod
>{:source-paths ["src/cljs"]
> :compiler {:output-to "
up id. I'm not sure what would
>> happen in the latter case, but the Clojars about doc (
>> https://github.com/ato/clojars-web/wiki/About#what-do-i-do-if-someones-taken-my-group-name)
>> says that one of the criteria for dispute resolution is demonstrated domain
>> ownersh
We need more information. What do your build settings look like?
Thanks,
David
On Sun, Jan 11, 2015 at 10:53 AM, Jonathon McKitrick
wrote:
> Is there a guide on how to combine optimization settings, source maps,
> externs, and maybe the preamble in the same project and/or build
> configuration?
ices Ltd. Are you associated with them?
>
> On Sat, Jan 10, 2015 at 12:27 PM, David Nolen
> wrote:
>
>> I'm happy to announce the release of Om 0.8.0. There's nothing much to
>> say over the last rc1 release. The biggest change is how you include Om as
>> a depen
I'm happy to announce the release of Om 0.8.0. There's nothing much to say
over the last rc1 release. The biggest change is how you include Om as a
dependency:
[org.om/om "0.8.0"]
https://github.com/swannodette/om
Have fun!
David
--
Note that posts from new members are moderated - please be pa
Wasn't saying it was wrong per se. Just code in go blocks incur overheads
unacceptable for inner loops. Unlikely to change anytime soon.
On Saturday, January 10, 2015, Marcus Lewis wrote:
> My paint function is basically
>
> (defn paint [ctx requests]
> (let [response (chan)]
> (put! reque
This is interesting but a very low priorty problem. Putting inner
loop computational work directly into go blocks like that really doesn't
make much sense due to the transformations. Things might get better when
ClojureScript gets the same code transformer as Clojure - they have
diverged for some t
On Fri, Jan 9, 2015 at 3:30 PM, David Nolen wrote:
> On Fri, Jan 9, 2015 at 3:20 PM, gvim wrote:
>
>> On 09/01/2015 19:45, David Nolen wrote:
>>
>>> https://github.com/clojure/clojurescript/wiki#compatible-
>>> clojure-contrib-libraries
>>&g
On Fri, Jan 9, 2015 at 3:20 PM, gvim wrote:
> On 09/01/2015 19:45, David Nolen wrote:
>
>> https://github.com/clojure/clojurescript/wiki#compatible-
>> clojure-contrib-libraries
>>
>>
> Do you have any experience of using Clojurescript within a project setup
&
https://github.com/clojure/clojurescript/wiki#compatible-clojure-contrib-libraries
On Fri, Jan 9, 2015 at 2:41 PM, gvim wrote:
> On 09/01/2015 19:02, David Nolen wrote:
>
>> On Fri, Jan 9, 2015 at 1:55 PM, gvim > <mailto:gvi...@gmail.com>> wrote:
>>
>&
On Fri, Jan 9, 2015 at 1:55 PM, gvim wrote:
> I have 3 questions regarding Clojurescript on NodeJS:
>
> 1. Optimisation
> Is optimisation relevant for NodeJS deployment? Many of the benefits of
> cljs optimisation seem to be related to JS in the browser. There are 2
> scenarios here - NodeJS modu
What operating system are you on?
On Thu, Jan 8, 2015 at 6:56 AM, Prabhas Pokharel wrote:
> Hi all,
> I am trying to run the new REPL as described by David in
> http://swannodette.github.io/2015/01/02/the-essence-of-clojurescript-redux/
> and am following the steps as described starting with `le
Other kinds of assets are out of scope and best handled by other tools.
On Wed, Jan 7, 2015 at 12:58 PM, Ivan L wrote:
> Sounds like this would work great for the majority where the lib is only
> js, but what about edge cases where a lib depends on a relative pathed
> resource like an image or c
I believe the solution to this problem has been sitting right under our
noses for some time.
I've written up my thoughts here:
http://dev.clojure.org/jira/browse/CLJS-965
Feedback & patch welcome :)
David
--
Note that posts from new members are moderated - please be patient with your
first po
haven't changed it's location or namespace form.
>
> I tried cleaning and deleting target and out dirs to no avail.
>
> I will fool with this some more and respond with and answer if I figure it
> out.
>
> any suggested directions would be appreciated.
>
> Tha
I haven't seen this. Does that namespace exist and where is located in your
source tree?
Also make sure you've actually cleaned your build, removed all cached
trampolines, removed target directory etc.
David
On Tue, Jan 6, 2015 at 4:13 PM, Brian Hurlow wrote:
> Hey All!
>
> Very excited to see
Could not locate
> cljsbuild/compiler__init.class or cljsbuild/compiler.clj on classpath: ,
> compiling:(/Users/jmckitrick/d
>
>
> On Monday, January 5, 2015 6:52:29 PM UTC-5, David Nolen wrote:
> > Seems like you have a stale cached trampoline - the caching around
> > Le
I suppose so, just using an async block just seems cleaner and simpler to
me and you're not modifying a type you don't control - not a big deal in
tests but you never know.
David
On Mon, Jan 5, 2015 at 9:12 PM, James MacAulay wrote:
> On Monday, 5 January 2015 20:00:17 UTC-5
On Mon, Jan 5, 2015 at 8:26 PM, Herwig Hochleitner
wrote:
> (deftest foo
> (async done ..)
> (async done ..))
>
> Should this be the user's responsibility?
Sure preventing this would be nice. Each test only needs a single async
block.
> By the same logic, IAsyncTest instances aren't easily c
That can't actually work since the go block doesn't receive the done
fn to proceed to the next test.
David
On Mon, Jan 5, 2015 at 7:13 PM, James MacAulay wrote:
> On Monday, 5 January 2015 14:30:35 UTC-5, David Nolen wrote:
>> The test runners should check for satisfies? IA
Seems like you have a stale cached trampoline - the caching around
Lein's fast trampoline doesn't seem very sophisticated. Erase
*-init.clj files, erase the target directory. Try again.
David
On Mon, Jan 5, 2015 at 6:48 PM, Jonathon McKitrick wrote:
> I'm following these instructions:
>
> http:/
You cannot use hash to generate unique IDs. Still this is a bug and a
JIRA ticket has already been filed -
http://dev.clojure.org/jira/browse/CLJS-962
David
On Mon, Jan 5, 2015 at 2:30 PM, Feng Xue wrote:
> These days, I was trying to utilize function hash in clojure/clojurescript to
> generate
Definitely plans to support async and happy to take a patch.
Basically I would like sugar that looks like this:
(deftest foo
(async done
...))
This desugars into:
(deftest foo
(reify
IAsyncTest
(-invoke [_ done]
...))
The test runners should check for satisfies? IAs
I've written up instructions on how to run ClojureScript REPLs without
using cljsbuild and other 3rd party tools -
https://github.com/clojure/clojurescript/wiki/Running-REPLs
On Sun, Jan 4, 2015 at 3:15 AM, Ivan L wrote:
> Would you expect the latest release to break cljsbuilds repl?
>
> I get t
The latest ClojureScript changes will break using cljsbuild and likely
others as the ClojureScript REPL runner. However this is a good time
to understand how to run REPLs directly without involving some other
tool -
https://github.com/clojure/clojurescript/wiki/Running-REPLs
David
--
Note that
fault
* CLJS-958: Node.js REPL: Upon error, last successfully item printed
On Fri, Jan 2, 2015 at 6:18 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New relea
:target option needs to be in the :compiler map.
On Sunday, January 4, 2015, Robin Ricard wrote:
> Hi there !
>
> I'm rather new with cljs and yesterday I tried to build my first cljs app
> using core.async & some Node.js APIs.
>
> I stumbled upon two issues:
>
> - One known issue that keeps cor
Tools will likely need updating for the latest changes as they tap into
details that may have changed that have no official API.
Still I suspect these changes will be small. Other than that, no, I suspect
in browser dev will be the same - just with a REPL experience more in line
with Clojure.
On
Non-stable releases of Node are not supported - 0.11.X, use a 0.10.X
release.
On Sunday, January 4, 2015, Max Gonzih wrote:
> Very nice! But I have issue that I saw also while applying instructions
> from previous blog post. Repl starts fine, but I see errors when I'm trying
> to evaluate anythi
Yes all REPLs that do not ship with ClojureScript will need updating. In
the meantime you can just use them directly instead of going through
cljsbuild. As I said above see the new mies template or the REPL runners
that come with ClojureScript to see how.
On Sunday, January 4, 2015, Ivan L wrote:
quot;Hi")
>
> ... which produced 'Hi' in the browser but produced only a carriage return
> in the terminal instead of returning the repl prompt. Attempts to use up
> arrow produced only ^[[A^[[A^[[A character sequences.
>
> I should add it's possible I may be
t
> readline unlike the leiningen Clojure repl.
>
> gvim
>
>
>
> On 02/01/2015 23:18, David Nolen wrote:
>
>> ClojureScript, the Clojure compiler that emits JavaScript source code.
>>
>> README and source code: https://github.com/clojure/clojurescript
&
Oops that should be 0.0-2657 of course.
David
On Sat, Jan 3, 2015 at 5:30 PM, David Nolen wrote:
> 0.0-2257 released, only change is the addition of `require-macros`
> REPL special function for importing macros from libraries like
> core.async.
>
> On Fri, Jan 2, 2015 at 6:18
0.0-2257 released, only change is the addition of `require-macros`
REPL special function for importing macros from libraries like
core.async.
On Fri, Jan 2, 2015 at 6:18 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and so
eload & :reload-all
On Fri, Jan 2, 2015 at 6:18 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New release version: 0.0-2644
>
> Leiningen dependency inf
ocket. (_stream_readable.js:746:14)
> at Socket.EventEmitter.emit (events.js:92:17)
> at emitReadable_ (_stream_readable.js:408:10)
> at emitReadable (_stream_readable.js:404:5)
> Error: Cannot find module 'C:GitClojureScriptSamplesmycljsprjout
> ode_repl_deps.js'
>
It just has known performance issues loading code - there's no interpreter
& warmup time is really bad.
On Saturday, January 3, 2015, Max Gonzih wrote:
> Any idea why Nashorn is slower? Is it related to type checks?
>
> --
> Note that posts from new members are moderated - please be patient with
process after which the shared infrastructure takes
over.
On Fri, Jan 2, 2015 at 6:18 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New release version: 0.0-264
I've posted a simple walkthrough of the new Node.js REPL:
http://swannodette.github.io/2015/01/02/the-essence-of-clojurescript-redux/
I suspect people will be reaching for ClojureScript REPLs
significantly more often than in the past :)
David
--
Note that posts from new members are moderated -
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2644
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2644"]
This release is one of the most significant in a ve
ries. With that out of the way we could
also think more seriously about :main and simplifying :none
development setups.
David
On Fri, Jan 2, 2015 at 4:49 PM, Logan Linn wrote:
> On Friday, January 2, 2015 10:27:52 AM UTC-8, David Nolen wrote:
>> Right the deps.clj pattern is now support
Right the deps.clj pattern is now supported, I'll update the README.
Thanks for pointing this out.
On Thu, Jan 1, 2015 at 7:56 AM, Kristofer Svärd
wrote:
> Den onsdagen den 31:e december 2014 kl. 21:22:41 UTC+1 skrev David Nolen:
>> I just cut Om 0.8.0-rc1. The only change fr
I just cut Om 0.8.0-rc1. The only change from prior betas/alphas is
more bug fixes.
https://github.com/swannodette/om
Feedback welcome!
David
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to
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 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
st.
>
> Is it a bug in cljs.test?
>
>
>
> On Wednesday, 24 December 2014 20:40:03 UTC+2, David Nolen wrote:
>> Time between releases are pretty variable though they tend to be
>> pretty frequent around new features like cljs.test as issues need to
>> be iro
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've spent the past week modifying the ClojureScript REPLs that ship
with ClojureScript to dramatically decrease boot time. The official
REPLs can now boot as quickly as 1 second or less.
The changes will no doubt have consequences for Austin, Weasel etc.
I've tried to describe the nature of the
If you or your team are using ClojureScript in production add an entry here:
https://github.com/clojure/clojurescript/wiki/Companies-Using-ClojureScript
Many thanks,
David
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message
There's been an explosion of ClojureScript libraries over the past
year. It would be nice to begin tracking them on the wiki so that
newcomers can more easily get their bearings:
If you have a ClojureScript library please add it to the following growing list:
https://github.com/clojure/clojurescr
Known issue: http://dev.clojure.org/jira/browse/CLJS-891
The problem is fundamental to Google Closure's approach to namespaces,
you'll encounter this even when you write Closure compatible
JavaScript.
A simple solution is just a compiler warning about such cases. I would
entertain a patch that do
Seems like a separate issue to me.
David
On Thu, Dec 25, 2014 at 3:25 PM, Sven Richter wrote:
> Hi,
>
> while I was preparing the bug report Captaion Obvious hit me again. This also
> occurs in clojure:
>
> As Thomas said, this is enough to reproduce it:
>
> (def a (atom #{}))
> (reset! a (into
I would actually consider this a core.async defect - the
interpretation of literals should not be different in go blocks. I
would open a core.async issue with all the details of this thread
summarized.
David
On Thu, Dec 25, 2014 at 12:14 PM, Sven Richter wrote:
> Hi Thomas,
>
> Thank you for inv
t; What is the usual delay (in days) between commit to the master and release?
>
> On Wednesday, 24 December 2014 20:18:39 UTC+2, David Nolen wrote:
>> The `are` macro isn't in a current release, however it's in master and
>> will appear in the next one. Otherwise Russe
Thanks for pointing this out. Fixed in master thanks to your patch.
Also landed a patch which should cover more problematic warning cases
around arithmetic.
David
On Wed, Dec 24, 2014 at 8:04 AM, Thomas Heller wrote:
> Hey,
>
> I just looked at the warnings code and it seems like a mistake that
gt;>
>>
>>
>> On Tuesday, December 23, 2014 1:59:45 PM UTC-8, Yehonathan Sharvit wrote:
>>>
>>> What is the gap between clojure.test and cljs.test?
>>>
>>> For exmaple: is the `are` macro implemented in cljs.test?
>>>
>>>
What version of Node.js?
On Tuesday, December 23, 2014, Andrew Keedle wrote:
> Never looked at Node before. I've followed the instructions, but I get
> this error when running: node run.js
>
> (I'm using nixos with node v0.11.13. Anyone got any clues?)
>
> [keeds@pixie:~/workspace/hello-world]$
cold start up times.
David
On Sun, Dec 21, 2014 at 1:12 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New release version: 0.0-2505
>
> Leiningen d
401 - 500 of 1042 matches
Mail list logo
