Amazing update! Yay.
But I just spotted one weird thing, after I pumped compiler version compilation
fails for me with following error:
clojure.lang.ExceptionInfo: failed compiling
file:public/javascripts/out-server-side/cljs/core.cljs {:file #File
I have a project which targets both Node.js and the browser - the vast majority
of code is shared and kept in the 'src' folder, with anything that needs to
differ being held in 'src-client' and 'src-server'. It's getting a little
clunky to maintain this, though, so I'm hoping to move everything
Looks like you're trying to use :cache-analysis with a higher
:optimizations setting than :none. I would avoid this for now.
http://dev.clojure.org/jira/browse/CLJS-1103
David
On Tue, Mar 10, 2015 at 6:07 AM, Max Gonzih gon...@gmail.com wrote:
Amazing update! Yay.
But I just spotted one
IMHO that is not something you should handle at compile time. I would suggest
creating a proper API and a main namespace that serves as an entry point to
your application and configures it before starting.
For example:
(ns my-app.log)
(defprotocol ILog
(-log [this msg]))
(def logger (atom
As of 0.0-3058 there's a new var *target* which is in fact a Google Closure
define.
You can use the following pattern.
(if (identical? *target* nodes)
...)
(if (identical? *target* default)
...)
HTH,
David
On Tue, Mar 10, 2015 at 6:53 AM, Greg g...@spinningatom.com wrote:
I have a
so much typos
s/pumped/bumped/
s/compiler/compiled/
sorry about that
On 03/10/2015 11:07 AM, Max Gonzih wrote:
Amazing update! Yay.
But I just spotted one weird thing, after I pumped compiler version compilation
fails for me with following error:
clojure.lang.ExceptionInfo: failed
On Tuesday, March 10, 2015 at 2:03:00 PM UTC+11, Mike Thompson wrote:
On Tuesday, March 10, 2015 at 2:14:42 AM UTC+11, Mike Haney wrote:
I'm really enjoying re-frame. I've tried several different architectures
over the last 6 months and ended up with something about 80% similar to the
Hopefully we can get that down 1s for anything except production builds.
Next on the list of todos is a shared AOT cache for all projects builds.
Once you've compiled a dependency from a JAR we should never compile it
ever again.
On Tue, Mar 10, 2015 at 9:11 AM, Chris McDevitt
On Tuesday, 10 March 2015 10:55:49 UTC, David Nolen wrote:
Looks like you're trying to use :cache-analysis with a higher :optimizations
setting than :none. I would avoid this for now.
That fixed the same problem for me. Thanks.
Also my cold compile time went down from 40s to 25s!
Thanks,
This is great, David!
Is it difficult to include dependencies (e.g., core.async) for a project built
this way?
--
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
I'm sure this has been asked more than once but the answer seems like a moving
target. What are some good ways to work with both clojure and clojurescript
code at the same time?
More specifically, how do you have your REPLs set up?
Currently, I use emacs + cider + weasel. After I start
Thanks for this, Mike. And thanks for the humor in your docs. I thoroughly
enjoy your writing style.
Cheers,
Jamie
On Mar 10, 2015, at 9:32 AM, Mike Thompson m.l.thompson...@gmail.com wrote:
On Tuesday, March 10, 2015 at 2:03:00 PM UTC+11, Mike Thompson wrote:
On Tuesday, March 10, 2015 at
This is puzzling. I have just run some tests and top level data structures do
appear to be eliminated.
For example: (def x {:a :b 2})
I was NOT able to find the string in the JavaScript compiled under
:optimizations :advanced.
Can you provide any more clarity on this rule?
I understand the practical futility of my call to have a standard for reusable
components that allows us as users to carry our investment forward to the next
great framework. But expressing it allows me to think a little deeper about the
possible solution.
Thank you for engaging and pouring
On March 10, 2015 at 11:31:29 AM, Marc Fawzi
(marc.fa...@gmail.com(mailto:marc.fa...@gmail.com)) wrote:
I understand the practical futility of my call to have a standard for
reusable components that allows us as users to carry our investment forward
to the next great framework. But
On Tuesday, March 10, 2015 at 4:18:41 PM UTC+11, marc fawzi wrote:
The miscommunication I see is this:
In many SPA frameworks like Angular and Ember, the resuable components cannot
work as is across frameworks. Therefore, they have certain dependencies on
the framework that cannot be
This issue from David Nolen, caught my eye:
https://github.com/andrewmcveigh/cljs-time/issues/21
Feels like there is important information there, but I just don't know enough
to interpret what's said. Can anyone help?
If I have this:
(def x {:a 1 :b 2})
David is saying that x can't be
17 matches
Mail list logo
