The problem is the reversing of the list if you want to convert back to a
list. You can avoid this but you have to use a custom mapping operation,
continuation passing style, and a trampoline - it won't be fast.
Another option is to realize that concrete types simply don't matter. What
you're tryi
It's common misconception that core.logic is a bunch of macros. The macros
are just sugar, there are functions for *everything*.
You can load a stream of "facts" however you please, you should look at
`to-stream` which can take any Clojure sequence of data and make it useable
from core.logic as a
Not a specific answer to your question, but it would be cool to see someone
make the core.match regex facilities handle this.
(match [msg]
[(#"^:(.*?)!.*PRIVMSG (.*) :(.*)" :>> [from to message])] ... true form
...
:else ... false form ..)
David
On Fri, Jun 21, 2013 at 11:43 AM, Steven D. A
I wasn't suggesting using Datomic.
On Fri, Jun 21, 2013 at 12:19 PM, Cedric Greevey wrote:
> On Fri, Jun 21, 2013 at 11:56 AM, David Nolen wrote:
>
>> Datomic integration notes on the core.logic wiki
>>
>
> I'm concerned with this trend towards favoring D
core.match 0.2.0-rc1 going out the door. ClojureScript support now up to
date with Clojure. I've also changed the ClojureScript version to optimize
for performance over code size as the code size issues are less problematic
for ClojureScript than they are for the JVM.
http://github.com/clojure/cor
I've written up how core.match works here
http://github.com/clojure/core.match/wiki/Understanding-the-algorithm
Hopefully this is a bit more approachable than the Maranget paper :)
On Mon, Jun 24, 2013 at 7:43 AM, David Nolen wrote:
> core.match 0.2.0-rc1 going out the door. Cloju
lojure and apart
> from this bug core.match just might finally make me do some serious testing.
>
> Cheers,
> /thomas
>
>
> On Monday, June 24, 2013 4:15:56 PM UTC+2, David Nolen wrote:
>
>> I've written up how core.match works here http://github.com/**
&
Yeah there's no "good" way to do this out of the box. You probably want to
define some custom constraints - to perform well you might even need to go
so far as to define a new constraint domain.
Things are not at the point where I feel comfortably describing how this
can be done as the details are
Wow, really? I didn't really consider it usable yet as we don't emit quite
enough information for mapping symbols.
On Tue, Jun 25, 2013 at 7:14 PM, wrote:
> Thanks a lot for the source map support. Made it possible for me to find
> the cause of my broken advanced compiled cljs. Without the sour
>
> On Tuesday, June 25, 2013 7:37:28 PM UTC-4, David Nolen wrote:
>
>> Wow, really? I didn't really consider it usable yet as we don't emit
>> quite enough information for mapping symbols.
>>
>>
>> On Tue, Jun 25, 2013 at 7:14 PM, wrote:
>>
&
tedious :)
>
> Gerrit
>
> Am Mittwoch, 26. Juni 2013 05:11:23 UTC+2 schrieb David Nolen:
> > I recall it adding a significant amount of time to advanced compilation
> so I'm not sure that's such a good idea as a default. But documenting and
> advertising its
t;
>
> Am Mittwoch, 26. Juni 2013 13:35:55 UTC+2 schrieb David Nolen:
>>
>> That's great to hear. Will update documentation in the appropriate places.
>>
>>
>> On Wed, Jun 26, 2013 at 4:01 AM, wrote:
>>
>>> Not sure why my previous post was del
Excellent!
I've been playing around the ClojureScript support ... needs work ... but
already A-M-A-Z-I-N-G.
David
On Fri, Jun 28, 2013 at 3:06 PM, Rich Hickey wrote:
> I've blogged a bit about the new core.async library:
>
> http://clojure.com/blog/2013/06/28/clojure-core-async-channels.html
Only experience will tell if setTimeout is a problem. I doubt it. I've
toyed around with a queueing dispatcher that waits till we get 32 events
with flush after 6ms (the time span between which mouse events may arrive
under OS X). This permits queueing and dispatching a million events in less
than
On Sun, Jun 30, 2013 at 7:46 PM, Brandon Bloom wrote:
> Two bits of core.async feedback:
>
> 1) The (let [c chan] (go ...) c) pattern is *extremely-common*. Might be
> nice to have something like (go-as c ...) that expands to that pattern.
>
My understanding with some member of the core.async tea
Because of blocking on read/write on unbuffered channels - users might need
more flexibility.
On Sun, Jun 30, 2013 at 8:13 PM, Brandon Bloom wrote:
> > My understanding with some member of the core.async team is that most
> channel based APIs fns should *take* a channel and only construct one as
Thanks for the report, that's definitely a bug and I know the cause:
http://dev.clojure.org/jira/browse/MATCH-80
David
On Wed, Jul 3, 2013 at 9:07 PM, Ben Wolfson wrote:
> This is with 0.2.0-rc2.
>
> This expression evaluates as expected:
>
> user> (m/match [:r :d]
>[:s :d] nil
0.2.0-rc3 going out with a fix.
On Wed, Jul 3, 2013 at 9:14 PM, David Nolen wrote:
> Thanks for the report, that's definitely a bug and I know the cause:
> http://dev.clojure.org/jira/browse/MATCH-80
>
> David
>
>
> On Wed, Jul 3, 2013 at 9:07 PM, Ben Wolfson wrot
Until core.logic gets environment trimming not a good idea as it us unable
to handle medium to large inputs.
David
On Thursday, July 4, 2013, Adam Saleh wrote:
> I was thinking about rewriting re-match in core.logic, so I am asking if
> somebody tried something similiar.
>
> My reasoning goes al
On Fri, Jul 5, 2013 at 1:13 PM, Adam Saleh wrote:
> Apologies, forgot that this is not a forum.
>
> 1) What would environment trimming provide me? Because right now I am
> using core.logic quite naively,
> mostly just applying recursion and some pattern matching.
>
Handling large inputs. If you'
This isn't a bug, you're in a infinite loop constructing go blocks. You
should probably move the loops into the go blocks.
David
On Sat, Jul 6, 2013 at 7:31 AM, MikeM wrote:
> Got an out of memory when experimenting with core.async channels in go
> blocks. The following is a simple example.
>
>
On Sat, Jul 6, 2013 at 12:27 PM, Norman Richards wrote:
>
> On Fri, Jul 5, 2013 at 1:06 PM, David Rocamora wrote:
>
>>
>> I'm trying to use featurec to describe some relationships within a nested
>> map. When I try to use it to find some keys in the map it returns nothing.
>> Here is an example:
This mostly looks good I remove the references to the defnc, fnc and predc
these are very experimental, likely to change, and easy to cause trouble if
you're not careful.
David
On Thu, Jul 11, 2013 at 1:06 PM, Benjamin Peter wrote:
> Hello,
>
> I went through the clojure core logic code and pic
Do you have a small failing example?
On Mon, Jul 15, 2013 at 12:08 PM, Michal Till wrote:
> I'm trying to match a false value of map's key (foo.bar) , which in
> javascript effectively means also undefined,null etc... It seems to me
> that core.match matches the value exactly. Is there any way
Yes that won't work. If something locks up the JavaScript process with an
infinite loop those other go blocks will never get a chance to run. I
believe even wrapping the final loop/recur in a go block won't help the
issue.
But I don't think this is a limitation in practice.
On Tue, Jul 16, 2013
Yet another core.match release candidate this time addressing outstanding
ClojureScript support issues as well as some breaking changes for
ClojureScript users - I've reorganized the namespaces, documented here -
http://github.com/clojure/core.match/blob/master/CHANGES.md
Feedback welcome!
http:/
While the macro can do what the original enhancement request suggested
that's not the actual problem the new threading macros were intended to
solve. They were primarily added to eliminate:
(let [x ...
x ...
x ...]
...)
Which is pretty ugly and also it's pretty easy to get into tro
Why not the following?
(let [stop (chan)]
(go (loop []
(println "Hello World!")
(let [[v c]] (alts! [(timeout 1) stop])]
(if (= c stop)
:done
(do (println "I'm done sleeping, going to recur now...")
(recur)))
On Wed, Jul 1
This is just a bug :when should only have special meaning if it occurs in a
list not a vector. Please file a ticket in JIRA:
http://dev.clojure.org/jira/browse/MATCH
David
On Sun, Jul 21, 2013 at 8:54 PM, Yong wrote:
> I have a sequence of keywords which I want to use match on. However, :when
More bug fixes - this time around locals matching in ClojureScript as well
as general bugs around vector patterns with rest patterns.
http://github.com/clojure/core.match
Feedback welcome!
David
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To
That's a hack for some versions of Safari and probably better handled
inside of render-loop. The problem is dispatch backed by MessageChannel in
Safari and seeing repaints.
On Sunday, August 4, 2013, Brent Millare wrote:
> From David Nolen's recent post with core.async,
> http://swannodette.githu
Very interesting. The rel feature is really still a bit of an experimental
thing and we'd like to replace it eventually with something less
problematic like pldb http://github.com/threatgrid/pldb.
Still, core.logic isn't really a database and your needs may be better
served by something with diffe
You can report issues here: http://dev.clojure.org/jira/browse/ASYNC
On Thu, Aug 8, 2013 at 7:02 AM, Kemar wrote:
> Hi there,
>
> it seems that loop bindings cant's see prior bindings made in
> the same loop when the loop is in a go block:
>
> (require '[clojure.core.async :refer [go]])
>> (go
I've since added an experimental Prolog style negation as failure
constraint `nafc`.
On Fri, Aug 9, 2013 at 5:19 PM, Alex Dowad wrote:
> Sorry to post on an old thread, but just in case someone comes here from
> Google:
>
> I'm just playing with core.logic, and I think I found a way to negate a
While I don't think I'd use it in your particular example, I like it when
it can eliminate superfluous let bindings.
(let [z (as-> (* x x) xsq
...)]
...)
On Mon, Aug 19, 2013 at 10:58 AM, Jay Fields wrote:
> In the past, I've written code like the following
>
> (defn foo [x y]
>
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-1859
Leiningen dependency information:
[org.clojure/clojurescript "0.0-1859"]
*Changes: *
* nth should only work in ISeq not Seqa
On Tue, Aug 27, 2013 at 10:51 AM, Mike Anderson <
mike.r.anderson...@gmail.com> wrote:
> To me it's all about consistency with other Clojure constructs. You can
> safely put nils in sequences, vectors, lists, sets etc.. nil is a valid
> "value" just like anything else. So why can't you put them in
ClojureScript has long represented symbols and keywords as JavaScript
Strings as a performance optimization around hash maps. However modern
JavaScript engines have shown that following Clojure JVM's design more
closely consistently delivers better performance.
Also the representation of keywords
>From 0.8.3 to 0.8.4
Fixes
* Allow fd/in to appear in any position
* LOGIC-127: nom-swapping now preserves vectors and maps
* LOGIC-132: proper recursive featurec
* LOGIC-139: fix unification on relations
Changes
* membero now uses disequality constraint
* docstring enhancements
h
Very cool stuff :) How much work would it take for this to work with
ClojureScript?
David
On Mon, Aug 26, 2013 at 4:47 AM, Maik Schünemann
wrote:
> Hi,
> I released a first version of my gsoc project expresso [1].
> This is an important Milestone in my gsoc project.
> What is there:
> an expres
t the compiling issue please post!
>
> I think it would be a good showcase for clojurescript to bring
> symbolic manipulation cababilities including solving equations etc to
> the browser.
>
> On Thu, Aug 29, 2013 at 10:19 PM, David Nolen
> wrote:
> > Very cool stuff :) H
On Fri, Aug 30, 2013 at 11:00 AM, Maik Schünemann wrote:
> I also think having expresso in clojurescript would be a cool think
> and I am willing to make a port after the gsoc period.
>
Cool.
> Do you know any good js or clojurescript (matrix) mathematical library
> which clojurescript express
On Tue, Sep 3, 2013 at 10:00 AM, bertschi
wrote:
> Whereas the first example receives all incremented values, the second one
> receives potentially less since both consumers read from the very same
> input channel! This also means that one can break working code, by
> (accidently) attaching an add
On Tue, Sep 3, 2013 at 10:00 AM, bertschi
wrote:
> Whereas the first example receives all incremented values, the second one
> receives potentially less since both consumers read from the very same
> input channel! This also means that one can break working code, by
> (accidently) attaching an add
On Tue, Sep 3, 2013 at 10:47 AM, bertschi
wrote:
> As far as I know, Haskell has Chan data types in its concurrency
> extensions, but I have never seen them in FRP. Maybe this means that FRP is
> addressing a different problem. On the other hand, the Automaton Arrow can
> be used to implement stat
The Clojure core.async captures bindings at the beginning of the go block.
This could be done in ClojureScript core.async as well but it needs
language support to do this correctly and efficiently.
David
On Thu, Sep 5, 2013 at 10:48 AM, Meikel Brandmeyer (kotarak)
wrote:
> Hi,
>
> Am Donnersta
e
> been able to find a cleaner, more functionally pure way of doing it that
> didn't require binding.
>
> Timothy
>
>
> On Thu, Sep 5, 2013 at 9:01 AM, David Nolen wrote:
>
>> I actually disagree a here as core.async brings a pretty nice concurrency
>> mod
On Thu, Sep 5, 2013 at 1:23 PM, Timothy Baldridge wrote:
> I used to think the same, until I wrote the current incarnation of the go
> macro in core.async. A few months back I ripped out all global vars (and
> bindings). The go "compiler" is now functionally pure, except for a single
> atom on the
Related - does using a purer approach hurt debugging and error
comprehension on the host - JVM / JavaScript?
On Thu, Sep 5, 2013 at 1:28 PM, David Nolen wrote:
> On Thu, Sep 5, 2013 at 1:23 PM, Timothy Baldridge wrote:
>
>> I used to think the same, until I wrote the current incarn
I actually disagree a here as core.async brings a pretty nice concurrency
model into play - I suspect there are instances where you might want to
construct a series of go blocks with some shared context that you'd rather
not put into every go loop.
In anycase improved binding support is something
SWEET!
On Fri, Sep 6, 2013 at 3:26 PM, Joel Holdbrooks wrote:
> Hi everyone,
>
> I put together a small library for wrapping the JavaScript console API
> available here: https://github.com/noprompt/shodan.
>
> This is nothing incredible but I decided to put it out there because I'm
> tired of co
In hunting down a ClojureScript bug I ended up fixing one of the biggest
bottlenecks in incremental ClojureScript builds.
If you use this branch
http://github.com/clojure/clojurescript/compare/509-protocol-warn you
should see up to 10X faster incremental builds in some cases. We're now
avoiding an
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-1877
Leiningen dependency information:
[org.clojure/clojurescript "0.0-1877"]
*Breaking Changes: *
* Keywords are no longer repre
gt; Thanks for the awesome work on ClojureScript,
> Julien
>
>
> Le dimanche 8 septembre 2013 20:42:51 UTC-3, David Nolen a écrit :
> > ClojureScript, the Clojure compiler that emits JavaScript source code.
> >
> >
> > README and source code: htt
Can't have thoughts without a lot more details :) Specific errors,
warnings, and a minimal case is always ideal.
David
On Mon, Sep 9, 2013 at 12:04 PM, wrote:
> A large percentage of tests for my core.async based library are failing.
> Any thoughts?
>
> --
> Note that posts from new members a
Nice work! :)
On Mon, Sep 9, 2013 at 9:39 PM, Alex Engelberg <
alex.benjamin.engelb...@gmail.com> wrote:
> http://github.com/aengelberg/clocop
>
> CloCoP is a Clojure wrapper of the Java library JaCoP. The acronyms stand
> for "Clojure/Java Constraint Programming". This invites comparison to the
1878 went out today, the only change was fixing a bug introduced by 1877
that caused spurious warnings when incrementally compiling.
On Mon, Sep 9, 2013 at 9:50 PM, Brandon Bloom wrote:
> > a (very) temporary workaround is to use the old code
>
> Why not just switch (k coll) to (get coll k) ?
>
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
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
>
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
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
--
You received this
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
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
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
, 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
:
> 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
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
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 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
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
> 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
Just released Om 0.8.7. The only change was bumping the cljsjs.react
dependency to get proper externs support.
David
On Mon, Jan 26, 2015 at 7:57 PM, David Nolen wrote:
> The only significant change is that Om now relies on the cljsjs.react
> artifact instead of the one I maintained
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2740
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2740"]
The primary reason for this release is to bring all
I mentioned trying this in a `let` binding instead. What happens when you
try that?
David
On Wed, Jan 28, 2015 at 9:04 AM, Crispin Wellington <
retrogradeor...@gmail.com> wrote:
> No, that's not it. So I tried:
>
> (def audio-context (js/AudioContext.))
> (.decodeAudioData audio-context (js/Arra
ough the project differences to
> see what's causing this. If I find anything, I'll post it.
>
> Thanks for your help
>
> Crispin
>
> On Wednesday, January 28, 2015 at 10:06:52 PM UTC+8, David Nolen wrote:
>>
>> I mentioned trying this in a `let` binding instea
gt; adding this tutorial to the Om Wiki. Otherwise, if you feel the extra
> dependency on Chestnut is also too much, I'll fork mies-om and add Figwheel
> there for the tutorial.
>
> After revising this work, I'll move on to the next tutorial.
>
> Best
>
> Sebas
r it should just start
> with a ready to go template "mies-om-wheel"?
>
> Thanks
>
> Sebastian Bensusan
>
> On Saturday, January 31, 2015 at 1:26:34 AM UTC+1, David Nolen wrote:
> > I would prefer just Figwheel. Relying only on Figwheel also means you
&
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2755
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2755"]
This release fixes regressions to the browser REPL
Just pushed out 0.0-2758. The only change was a fix for the macro usage
enhancement.
On Sun, Feb 1, 2015 at 5:38 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
&
And just pushed out 0.0-2760 which catches a ns spec parsing regression
caught by some helpful people in the ClojureScript IRC channel.
David
On Mon, Feb 2, 2015 at 9:22 AM, David Nolen wrote:
> Just pushed out 0.0-2758. The only change was a fix for the macro usage
> enhancement.
>
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2814
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2814"]
There are numerous enhancements in this release inc
Oh also thanks to Leon Grapenthin for working on the async testing support.
And of course a general round of thanks to everyone who submitted patches
of any kind and size for this release.
David
On Mon, Feb 9, 2015 at 7:47 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that em
Cut 0.0-2816. The only change is a fix for reader metadata leakage around
`reify`.
David
On Mon, Feb 9, 2015 at 7:47 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescrip
On Wed, Feb 11, 2015 at 6:52 AM, Daniel Skarda wrote:
> Could you please write few examples how to take advantage of new unified
> source-map support? I tried 0.0-2816 with node.js without success. I tried
> with piggieback and without. But the only solution was with 'npm install
> source-map-sup
You can run tests in any REPL that ships with ClojureScript - we include
two JVM based ones Rhino and Nashorn. Rhino is older and more mature.
Nashorn probably needs some further work to be good for testing. Patches
welcome. Both of these options suffer from different forms of slowness
(Rhino is ju
This message is mostly aimed at Clojure and ClojureScript REPL developers -
Cider, Weasel, etc. I've written up some details on how to integrate the
new automatic source mapping functionality:
https://github.com/clojure/clojurescript/wiki/Custom-REPLs#source-mapping
Feedback welcome and preferabl
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2843
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2843"]
This release is primarily about outstanding Node.js
Just pushed out 0.0-2850. The only significant change is a critical fix for
dependent namespace recompilation spotted by Bruce Hauman.
David
On Thu, Feb 12, 2015 at 12:08 PM, David Nolen
wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and so
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2913
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2913"]
This release comes with two very big enhancements.
ljsbuild to support this.
> On Saturday, February 21, 2015 at 3:16:11 PM UTC-6, Boris Kourtoukov wrote:
> > On Saturday, February 21, 2015 at 1:01:39 PM UTC-5, David Nolen wrote:
> > > ClojureScript, the Clojure compiler that emits JavaScript source code.
> > >
>
Posted here:
http://swannodette.github.io/2015/02/23/hello-google-closure-modules/
David
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - pl
:preamble will only be applied to the base module. When using :modules
there is not such thing as a main output file.
You cannot currently have a per module :preamble.
David
On Tue, Feb 24, 2015 at 6:25 AM, Max Gonzih wrote:
> On Saturday, February 21, 2015 at 7:01:39 PM UTC+1, David No
If you have a ClojureScript based product and your customers use FireFox
Nightly you will encounter trouble due to a RegExp detection bug in prior
ClojureScript releases interacting with recent Firefox ES6 related changes.
Here's the ticket:
https://bugzilla.mozilla.org/show_bug.cgi?id=1138325
We
tchel Kuijpers
wrote:
> On Tuesday, March 3, 2015 at 11:12:03 PM UTC+1, David Nolen wrote:
> > If you have a ClojureScript based product and your customers use FireFox
> Nightly you will encounter trouble due to a RegExp detection bug in prior
> ClojureScript releases interacting wit
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-3058
Leiningen dependency information:
[org.clojure/clojurescript "0.0-3058"]
This is a significant enhancement release around RE
1)
> at
> cljs.compiler$compile_file_STAR_$fn__2927.invoke(compiler.clj:1055)
> at cljs.compiler$with_core_cljs.invoke(compiler.clj:961)
> at cljs.compiler$compile_file_STAR_.invoke(compiler.clj:981)
> at cljs.compiler$compile_file$fn__2959.invoke(compiler.cl
hermcdev...@gmail.com
> wrote:
> 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.
It's no more or less difficult than using Clojure by itself. You can use
whatever tool you want to manage dependencies.
That said I would probably use Maven or Lein myself. Using Maven directly
with AOTed dependencies will likely result in a fast workflow. AOTed
tools.reader and data.json JARs are
h can be a little finicky particularly in Safari in my experience.
HTH,
David
On Wed, Mar 11, 2015 at 9:38 AM, Peter West wrote:
> On Tuesday, 10 March 2015 09:41:45 UTC+10, David Nolen wrote:
> > ClojureScript, the Clojure compiler that emits JavaScript source code.
> >
> >
ClojureScript, downstream tooling, and the interactions between have become
sufficiently complex enough that we no longer have time to consider
anything that may originate downstream.
Please be sure read and understand the following before reporting
ClojureScript issues moving forward:
https://gi
401 - 500 of 2147 matches
Mail list logo
