Please see https://clojurescript.org/news/2024-01-24-release for details.
Thanks!
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 -
Please see https://clojurescript.org/news/2021-12-20-release for details.
Thanks!
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 -
Please see https://clojurescript.org/news/2021-11-04-release for details
Thanks!
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 -
Please see https://clojurescript.org/news/2021-05-24-release for details.
Thanks!
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 -
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Please refer to the announce post for the details:
https://clojurescript.org/news/2021-04-06-release
As always, feedback welcome!
David
--
You received this
In the async case just handle the error yourself and fail the test. There's
really not a good way to detect async errors since there isn't one way to.
do async (promises, core.async, etc.).
David
On Wed, Nov 25, 2020 at 1:19 AM Stuart Campbell wrote:
> That unfortunately doesn't work for async
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Please refer to the announce post for the details:
https://clojurescript.org/news/2020-04-24-release
This release also features a significant enhancement when
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Please refer to the announce post for the details:
https://clojurescript.org/news/2019-01-31-release
As always, feedback welcome!
--
You received this
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.10.439"]
Please refer the announce post for the details:
1.10.329 was released today, it addresses a few minor issues in 312
including an externs inference bug.
David
On Fri, Jun 15, 2018 at 10:50 AM, David Nolen
wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.co
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.10.312"]
This release contains many fixes and enhancements, the most notable being
those
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.10.238"]
This release contains a very large number of enhancements. Please
refer to the
ou can see, the RN/JS stack traces are not very useful in this case.
> I can dig deeper if needed to find exactly where it fails (I have a few
> places where I use RegExp).
>
> Thanks all!
> Rangel
>
>
> On Friday, May 12, 2017 at 1:31:54 PM UTC-7, David Nolen wrote:
>>
>
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.946"]
This release contains many bug fixes and addresses feedback from the 1.9.908
release.
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.908"]
This release includes a number of bug fixes and changes based on feedback
from the
y management in general, does this release obsolete
> cljsjs for new projects and what is the new method?
>
>
> On Friday, July 28, 2017 at 4:55:04 PM UTC-5, David Nolen wrote:
>>
>> ClojureScript, the Clojure compiler that emits JavaScript source code.
>>
>> RE
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.854"]
This is a significant feature release. Notable new features include
comprehensive NPM
3rd post in the series is now up thanks to Mike Fixes
https://clojurescript.org/news/2017-07-14-checked-array-access
On Mon, Jul 10, 2017 at 5:28 PM, David Nolen <dnolen.li...@gmail.com> wrote:
> We have a series of blog posts in the queue that outline several major
>
Second post in the series is up
https://clojurescript.org/news/2017-07-12-clojurescript-is-not-an-island-integrating-node-modules
kindly contributed by António Nuno Monteiro.
Enjoy!
David
On Mon, Jul 10, 2017 at 5:28 PM, David Nolen <dnolen.li...@gmail.com> wrote:
> We have a serie
We have a series of blog posts in the queue that outline several major
enhancements to the ClojureScript compiler that will be available in the
next release. This is the first one in the series:
https://clojurescript.org/news/2017-07-10-code-splitting
Enjoy!
David
--
You received this message
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.671"]
This is a follow up bugfix release to 1.9.660.
As always, feedback welcome!
##
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.660"]
This release includes many performance enhancements to the
ClojureScript compiler as
On Sat, Jun 24, 2017 at 1:49 PM, Matching Socks
wrote:
>
> At any rate, I would like to put in either a documentation issue (if it's
> a feature that ClojureScript's "case" does not work like Clojure's) or else
> a defect issue (if it's a bug).
>
As I stated earlier, we're
I agree that this behavior diverges from Clojure's and that we probably
should have thought it through a bit more 2 years ago. But at this point
it's probably water under the bridge. Anybody that's actually relying on
this behavior is likely inlining named numeric constants to make jump
tables.
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.562"]
This release coincides with Clojure 1.9.0-alpha17, includes a variety
of fixes, and
ect (evaluating 'schema.core.MapEntry.
> prototype')
>
> I'm assuming that is related to this change, but I'll need to investigate
> more. There's already a merged PR for schema that excludes MapEntry in
> refer-clojure. I'm hoping that will fix this.
>
>
> maanantai 15. toukokuuta 20
That's just a warning. Is there some deeper breakage that you are observing?
David
On Sun, May 14, 2017 at 3:09 AM, Tatu Tarvainen wrote:
>
> > * CLJS-2013 - Add MapEntry type
>
> This change seems to break plumatic schema, after upgrading I'm getting
> warnings:
>
>
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.542"]
This release is primarily about staying in sync with the latest changes to
spec. It
I just cut 1.9.521. The only change was to fix a regression to
:foreign-libs when there are multiple entries which use the same :file.
David
On Wed, Apr 12, 2017 at 4:52 PM, David Nolen <dnolen.li...@gmail.com> wrote:
> ClojureScript, the Clojure compiler that emits JavaScript so
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.518"]
This release bumps Closure Compiler, finally resolving the issue with
core.async.
As
This is correct.
On Thu, Mar 9, 2017 at 2:36 AM, Colin Fleming
wrote:
> I believe that dependency is because Google Closure requires it.
>
> On 9 March 2017 at 16:45, Mike Rodriguez wrote:
>
>> Guava is often a dependency conflict when trying to
Just cut 1.9.494 to back out some macros that were made unintentionally
private.
On Fri, Feb 24, 2017 at 4:47 PM, David Nolen <dnolen.li...@gmail.com> wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://git
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.493"]
This is a bugfix release.
As always, feedback welcome!
### Fixes
* CLJS-1948:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.473"]
This is a bugfix release.
As always, feedback welcome!
## Fixes
* CLJS-1931: Closure
Looks like you have a dependency issue. Use `lein deps :tree` or the
equivalent command to sort it out.
HTH
David
On Saturday, January 28, 2017, Francesco Bellomi <
francesco.bell...@gmail.com> wrote:
> Hi,
>
> first of all, congratulations on this release, it's a huge step ahead.
>
> I'm
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.456"]
This is a significant feature release.
The first new feature is externs inference.
`require` only works if your namespace is in a file that respects Java
classpath conventions. You may have missed this detail in the way all the
Quick Start examples are structured.
HTH,
David
On Sat, Jan 30, 2016 at 12:17 PM, Gregg Reynolds wrote:
> I'm following the
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.293"]
This release fixes a major issue with transit analysis caching where
files were
This issue is fixed in master now thanks to Thomas Heller. The performance
hit is negligible.
Thank you for the report.
David
On Tue, Oct 18, 2016 at 3:45 PM, John Szakmeister
wrote:
> On Tue, Oct 18, 2016 at 5:59 AM, Thomas Heller
> wrote:
> >
and might break a lot of other
> things I currently don't understand. Also performance could get a hit.
>
> Better ideas, anyone? :-)
>
> ps. don't use :advanced mode when programming atomic reactors in
> ClojureScript ;-p
>
> On Saturday, October 15, 2016 at 10:59:14 PM UTC
This issue is somewhat to be expected if you're going to use `js->clj`.
This issue has nothing to do with ClojureScript compiler versions - you
just got lucky before. Google Closure will collapse properties, but some of
these collapsed properties are going to be used to determine protocol
Oops don't think so. If you have a patch, that would be welcome.
David
On Tue, Sep 13, 2016 at 3:45 AM, 'Burt' via Clojure <
clojure@googlegroups.com> wrote:
> Hi,
>
> with "1.9.0-alpha10" and core.logic "0.8.10":
>
> (ns lwb.nd.rules
> (:refer-clojure :exclude [==])
> (:require
I just cut 1.9.229. It includes a spec fix as well as a bug around
computing the js dependency index in the presence of .cljc & .cljs files
with the same namespace.
On Fri, Aug 26, 2016 at 6:02 PM, David Nolen <dnolen.li...@gmail.com> wrote:
> I just cut 1.9.227. The only change
I just cut 1.9.227. The only change was a warning regression around
cljs.core excludes
David
On Fri, Aug 19, 2016 at 1:40 PM, David Nolen <dnolen.li...@gmail.com> wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: htt
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.225"]
A bug fix release for cljs.spec and a REPL regression.
As always feedback welcome!
I just cut 1.9.216, the relevant changes are fixing a regression around
instrumenting multi-arity fns and adding spec assert.
On Mon, Aug 15, 2016 at 8:58 AM, David Nolen <dnolen.li...@gmail.com> wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
&
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.211"]
This release addresses a few bugs around cljs.spec discovered in the
last release
.clj:190)
> at clojure.lang.AFn.run(AFn.java:22)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.198"]
This release brings cljs.spec to parity with Clojure
1.9.0-alpha10. This release
clojure.spec already does this by communicating the path where the failure
occurred. Also if you use s/cat you can label the arguments which I think
is probably more friendly and you'll still get the path.
(require '[cljs.spec :as s])
(defn foo [a b c] (+ a b c))
(s/fdef foo
:args (s/cat :a
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.89"]
This release fixes several cljs.spec issues. It also includes a new
compiler option
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.76"]
This release brings cljs.spec to parity with Clojure 1.9.0-alpha7. It
addresses an
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.36"]
This release fixes a cljs.spec bug around instrumented multi-arity
fns. It also
Choosing cljs.spec over clojure.spec is out of necessity not preference -
Clojure has already taken the namespace and that namespace defines macros.
We are considering aliasing support for cljs.spec. That is rewriting
clojure.spec vars in ClojureScript sources to cljs.spec but it will likely
Nothing to do with macros, that wouldn't work in Clojure either, the
problem is only the namespaced keyword - ::tiltontec.qxia.base/m.Composite
Note the leading double colon, ::
The :: indicates that tiltontec.qxia.base is an ns alias, which clearly
it's not since it's the fully qualified name.
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.14"]
This release includes a complete and faithful port of clojure.spec to
clojure.spec has been ported to cljs.spec now available in ClojureScript
master. Will probably cut a release later next week but users are
encouraged to build master and give it a spin.
David
On Mon, May 23, 2016 at 10:12 AM, Rich Hickey wrote:
> Introducing clojure.spec
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.8.51"]
This release updates the Closure Compiler and tools.reader dependencies,
fixes a
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.8.40"]
This release addresses some minor unintentional interactions with 3rd party
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.8.34"]
There are many minor fixes in this release around bootstrapped
ClojureScript. This
seems fine.
>
> Rangel
>
> On Friday, March 18, 2016 at 11:04:46 AM UTC-7, David Nolen wrote:
>>
>> ClojureScript, the Clojure compiler that emits JavaScript source code.
>>
>> README and source code: https://github.com/clojure/clojurescript
>>
>> Leining
Capital One's Level Money https://www.levelmoney.com
Thomas Reuters https://open.mediaexpress.reuters.com
There's a list of companies that gets periodically updated here:
https://github.com/clojure/clojurescript/wiki/Companies-Using-ClojureScript
David
On Tue, Mar 1, 2016 at 1:10 AM, Alex
Hello,
We're approaching the end of the application period for organisation
participation in Google Summer of Code 2016. This is a fantastic
program that helps grow open source communities and gives students
from around the world the opportunity to get paid to work on open
source over the course
If you need eval then you need to be OK with pulling in a lot of code and
giving up Closure advanced optimizations and dead code elimination.
Whatever small size savings an interpreter might offer, it would still
suffer from this fundamental problem.
David
On Sat, Feb 13, 2016 at 1:58 PM, ru
.charCodeAt is the correct thing - there is no real char type in
ClojureScript only strings.
David
On Tue, Feb 9, 2016 at 1:01 PM, nick rothwell wrote:
> Dumb question: should I be able to get the ordinal value of a character in
> ClojureScript via something like
>
> (int \A)
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.7.228"]
The primary feature of this release is a new experimental compiler
flag -
core.match will attempt to optimize matching :when clauses in the decision
tree.
David
On Tue, Dec 8, 2015 at 4:18 PM, retnuH wrote:
> I can't really figure out what the deal is with predicates. They're not
> mentioned in the Basic/Advanced usage wiki pages at all. The code
The rationale is simply that Prolog-like systems have embraced it as it
appears to be a very natural fit - https://dtai.cs.kuleuven.be/problog/
David
On Wed, Nov 25, 2015 at 9:20 AM, Dragan Djuric wrote:
> I know well how probabilistic logic works. It is a superset of the
>
Definitely interested in it! But I don't have time to work on it myself. So
the likelihood of this feature landing is entirely dependent on
contributions :)
HTH,
David
On Fri, Nov 20, 2015 at 7:01 AM, Henrik Larsson
wrote:
> I have started to play around with ProbLog2
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.7.170"]
This release includes a major refactor of the build pipeline thanks to
Juho
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.7.145"]
This release updates the Google Closure Compiler dependency and
includes many
ate...@gmail.com> wrote:
> On Tuesday, October 13, 2015 at 8:02:07 AM UTC-7, David Nolen wrote:
> > ClojureScript, the Clojure compiler that emits JavaScript source code.
> >
> >
> > README and source code: https://github.com/clojure/clojurescript
> >
&
having some
trouble compiling a macro via defmacro.
Matt
On Saturday, August 1, 2015 at 1:52:23 AM UTC+8, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript 1.7.48]
This release updates the Google Closure Compiler and Library
dependencies to the
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript 1.7.28]
ClojureScript now has a proper version number. This version number is
designed to
Some more words demos here
http://swannodette.github.io/2015/07/29/clojurescript-17/
Cheers,
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
Just isn't supported. Patch welcome :)
David
On Wed, Jul 1, 2015 at 3:46 PM, Alan Thompson clooj...@gmail.com wrote:
Hi - I am trying to write some unit tests for Datomic using core.match to
keep things succinct. I was hoping to use a match pattern like this:
[ {:e tx-eid :a
http://annapawlicka.com/travis-ci-and-clojurescript-tests/ is probably
a more relevant basic guide.
On Tuesday, June 30, 2015, Nathan Marz nat...@nathanmarz.com wrote:
I'm trying to get Specter's tests running under ClojureScript. I can run
the tests manually in a REPL just fine, but I cannot
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript 0.0-3308]
This release bumps the Clojure dependecy to 1.7.0-RC1 and includes fixes
and minor
People have been asking about cljs.test usage for a while now. I've finally
written up some notes https://github.com/clojure/clojurescript/wiki/Testing.
Feel free to edit for clarity / typos etc.
David
--
You received this message because you are subscribed to the Google
Groups Clojure group.
Also using `lein run` without supplying correct JVM settings (like -server)
is going to lead to pretty misleading results.
On Thu, May 14, 2015 at 3:44 PM, Alex Miller a...@puredanger.com wrote:
The major problem here is that you are using boxed math for everything
instead of primitives.
0)
Enhancing :libs support was pretty finicky work so I'm not particularly
surprised by the regression. Looking into it. In the meantime you don't
need specify each library, `:libs [lib]` should suffice.
David
On Mon, May 11, 2015 at 1:10 AM, Ruslan Prokopchuk fer.ob...@gmail.com
wrote:
With 3269
not
locate cljs/repl__init.class or cljs/repl.clj on classpath: ,
compiling:(figwheel_sidecar/repl.clj:1:1)
On Sunday, May 10, 2015 at 10:20:13 AM UTC-4, David Nolen wrote:
Just cut 0.0-3269 which adds the missing analysis and source map bits
back into the artifacts. It also cleans up :libs
, May 10, 2015 at 10:20:13 AM UTC-4, David Nolen wrote:
Just cut 0.0-3269 which adds the missing analysis and source map bits
back into the artifacts. It also cleans up :libs support and fixes a
related regression with Closure compatible libraries that follow classpath
conventions (like transit-js
Closure compatible libraries now enjoy REPL support.
David
On Sun, May 10, 2015 at 9:41 AM, David Nolen dnolen.li...@gmail.com wrote:
It appears there are still some important bits missing from the artifacts.
Working through the issues and will cut a release soon.
David
On Sun, May 10, 2015
$_cache_protocol_fn.invoke (core_deftype.clj:554)
0.0-3255 seems fine.
@raspasov
On Saturday, May 9, 2015 at 12:33:52 PM UTC-7, David Nolen wrote:
Just released 0.0-3264, it fixes a critical issue where .js files were
missing from the artifacts due to the changed build. Also included are a
several fixes
Just released 0.0-3264, it fixes a critical issue where .js files were
missing from the artifacts due to the changed build. Also included are a
several fixes around the :libs feature, REPLs, and stack trace mapping.
David
On Fri, May 8, 2015 at 3:23 PM, David Nolen dnolen.li...@gmail.com wrote
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript 0.0-3255]
A big thanks goes out to Jonathan Boston and Shaun Lebron for this
release. Thanks
]
[org.clojure/data.json 0.2.6 :classifier aot]
Should do the trick and should significantly improve cold compile and REPL
start times. Feedback on the AOTed ClojureScript artifact is most welcome.
David
On Fri, May 8, 2015 at 3:23 PM, David Nolen dnolen.li...@gmail.com wrote:
ClojureScript, the Clojure
A quick glance at your benchmarking setup, it's not clear that you are
benchmarking what you think you are benchmarking, and jsperf is not a
suitable benchmarking harness (irrespective of it's popularity).
Benchmarking is hard, benchmarking JavaScript is harder, and benchmarking
JavaScript that
Nearly all the performance notes about Clojure multimethods apply to
ClojureScript.
On Saturday, April 25, 2015, Alex Miller a...@puredanger.com wrote:
I should say all of that is for Clojure and likely bears no similarity to
the nuances in ClojureScript.
On Saturday, April 25, 2015 at
You need to make sure some other dependency isn't pulling in a different
version of tools.reader.
David
On Sat, Apr 25, 2015 at 11:11 PM, Allen Rohner aroh...@gmail.com wrote:
On Saturday, April 25, 2015 at 12:02:08 PM UTC-5, Mike Fikes wrote:
Hey Tony, try updating the version of Clojure
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript 0.0-3211]
This release is a bugfix release addressing some regressions as well
as introducing
The only reason :default exists is because *anything* in JavaScript can be
thrown and there needs to be some way to catch non-Error derived values.
This is not the case for Java of course. :default could probably be aliased
to Throwable, but in the meantime differences like this are now handleable
I was able to connect IntelliJ to a REPL because Cursive can now connect to
a ClojureScript REPL started in the usual way. There is no special setup,
make sure you've taken the time to read the new ClojureScript Quick Start.
HTH,
David
On Sat, Apr 11, 2015 at 5:06 AM, Georgi Danov
in normal JVM
process, is this how it's supposed to be?
On Saturday, April 11, 2015 at 4:06:47 PM UTC+2, David Nolen wrote:
I was able to connect IntelliJ to a REPL because Cursive can now connect
to a ClojureScript REPL started in the usual way. There is no special
setup, make sure you've
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript 0.0-3196]
This release is intended to coincide with Clojure 1.7.0-beta1. Besides
conditional
This is part of the proposed GSoC ClojureScript Closure project so we're
likely to see support for this by sometime this fall.
Dvid
On Mon, Mar 23, 2015 at 10:42 PM, james borden jmbor...@gmail.com wrote:
Is there a way to automatically generate externs files for js libraries
for use with
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-3126
Leiningen dependency information:
[org.clojure/clojurescript 0.0-3126]
This release just fixes a minor REPL related
Yes I said earlier that you'll want SNAPSHOT releases of both weasel and
piggieback. The current release of piggieback doesn't include this commit
https://github.com/cemerick/piggieback/commit/966c811ab817df0e818404943c473081337b286e
In the case of weasel you might want to try a local install of
1 - 100 of 2038 matches
Mail list logo