ANN: core.logic 0.8.6

The main change is the introduction of a new protocol IVerifyConstraint. Implementations of it will be called before a constraint is added to the constraint store - this is the hook needed for detecting incompatible constraints. More information here: http://github.com/clojure/core.logic Feedback

Re: ANN: core.logic 0.8.6

u recommend for someone who wants to try and understand core.logic? > > Thank you > > Plinio Balduino > > > On Saturday, February 8, 2014, David Nolen wrote: > >> The main change is the introduction of a new protocol IVerifyConstraint. >> Implementations of it w

ANN: core.logic 0.8.7

This release just fixes a bug around aliased logic vars and the new constraint verification functionality. More information here: http://github.com/clojure/core.logic Feedback welcome! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this

ANN: om-sync

I've been banging the drum about Om & modularity for a while now and I've come up with the very beginning of a simple reusable component that I think demonstrates the power of Om's emphasis on modularity and application wide state management: http://github.com/swannodette/om-sync The whole point

ANN: Om 0.4.0

Happy to announce a new release of Om. There are some breaking changes mostly to make the API more uniform - om.core/root was needlessly different from om.core/build. The biggest and most exciting change is the inclusion of the :tx-listen option to om.core/root. This will setup a callback which wi

Re: ANN: Om 0.4.0

Om 0.4.0 requires ClojureScript 0.0-2156, also looks like you need to run a `lein cljsbuild clean`. David On Fri, Feb 14, 2014 at 8:00 AM, Tatu Tarvainen wrote: > > Btw, I seem to get the following compiler errors after upgrading om from > 0.3.6 to 0.4.0 > > (clojurescript version is 0.0-2138)

Re: Using core.logic to implement data strutures (CTMCP)

You will need to implement unification for your record type. I recommend just using simpler data structures unless how to do this is apparent to you - it's not particularly difficult but you need to go to the source if you want to understand how to make it work. David On Fri, Feb 14, 2014 at 1:1

Re: [ANN] Clojure 1.6.0-beta1

exists? doesn't seem right to me. Also we do use `exists?` currently in ClojureScript since feature detection is so common in client side code and the name seems more appropriate to me in that context. That could of course change but we would need to coordinate. David On Fri, Feb 14, 2014 at 3:2

Re: [ANN] Clojure 1.6.0-beta1

Also I think the ship on overloading some already sailed with some-> and some->> David On Fri, Feb 14, 2014 at 3:27 PM, Dom Kiva-Meyer wrote: > Great changes! I have a question about #5. > > >> 5) New "some" operations >> Many conditional functions rely on logical truth (where "falsey" >> valu

Re: [ANN] Clojure 1.6.0-beta1

ld thus argue, that a name with a higher degree of precision, and > perhaps more characters, would have been a better choice. > > On Friday, February 14, 2014 2:36:51 PM UTC-8, David Nolen wrote: > >> exists? doesn't seem right to me. Also we do use `exists?` currently in >

Re: [ANN] Clojure 1.6.0-beta1

missed the boat. :-) > > Did that discussion take place here or in Jira? I'd definitely like to be > able to chime in with thoughts/suggestions in the future WRT this topic. > > On Friday, February 14, 2014 7:46:23 PM UTC-8, David Nolen wrote: > >> exists? is a pretty c

Re: ANN: Om 0.4.0

compiled "examples/graft/main.js" in 3.459 seconds. > Compiling "examples/tests/main.js" from ["src" "examples/tests/src"]... > Compiling "examples/tests/main.js" failed. > java.io.FileNotFoundException: examples/tests/src (No such file or > d

Re: clojurescript source maps: chrome's expected behavior, firefox support

On Mon, Feb 17, 2014 at 3:43 AM, Ransom Williams wrote: > First of all thanks to everyone working on clojure for making web > development suck less. I recently sandboxed a clojure server application, > and the tooling, documentation, and availability of libraries are all > awesome. > > Anyway, I'

Re: weird bug with cljs.core.async + macros

Due to asm.js some JS engines are starting to compile switch statements where the cases are integers into jump tables. Compiler enhancement that compiles optimizable case expressions to JS switch statements would be a welcome enhancement - http://dev.clojure.org/jira/browse/CLJS-713. David On Tu

ANN: Om 0.5.0-rc1

In order to stay in sync with React 0.9.0-rc1 I've cut Om 0.5.0-rc1. There are a couple of small breaking changes due to React but otherwise the differences between 0.4.2 and 0.5.0-rc1 are minor. One big enhancement is that you can now render to a string with om.dom/render-to-str. Another big enha

ANN: Om 0.5.0

The only change is that we now depend on the just released React 0.9.0. Feedback welcome! https://github.com/swannodette/om 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 tha

ANN: ClojureScript 0.0-2173

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2173 Leiningen dependency information: [org.clojure/clojurescript "0.0-2173"] Changes & Enhancements: * IAtom marker protocol * I

Re: Macro writing macro fails with CLJS

You shouldn't use js*, and in this case it can be avoided. The problem you're encountering is a long outstanding wart that ClojureScript macros resolve symbols in Clojure not ClojureScript. Instead of + (which is actually clojure.core/+) you want to specify cljs.core/+: (defmathop cljs.core/+ cljs

Re: Macro writing macro fails with CLJS

(macromath/macros.clj:58:1) > > I also tried to require cljs.core in that macro's namespace, but then > it complains this way: > > clojure.lang.Compiler$CompilerException: java.lang.RuntimeException: > Can't take value of a macro: #'cljs.core/+, > compiling:(macroma

Re: Om: trouble with goog reference

The issue is that advanced compilation produces a single artifact. David On Sun, Feb 23, 2014 at 8:22 PM, boz wrote: > I'm having trouble with the Om basic tutorial Higher Order > Components > using > emacs a

Enhanced Node.js support in ClojureScript master

At long last the ClojureScript compiler can now target Node.js under optimizations :whitespace or :none as of this commit: http://github.com/clojure/clojurescript/commit/0c7b31ada01237de33cef77b817ccef3f2b3576d Some basic notes here: http://github.com/clojure/clojurescript/wiki/Quick-Start#wiki-no

Re: Macro writing macro fails with CLJS

k you - that > change does work indeed! But then why does my original version work in > Clojure? A change in quoting usually only causes havok/failure, but > here it doesn't seem to... > > Thanks again! K. > > > On 23 February 2014 22:15, David Nolen wrote: > >

Re: [GSoC]: We made it! Clojure is a Google Summer of Code 2014 menoring organisation

Awesome! On Mon, Feb 24, 2014 at 2:06 PM, Daniel Solano Gómez wrote: > Hello, all, > > I am happy to report that Clojure has been accepted as a Google Summer > of Code 2014 mentoring organisation. I'd like to thank everyone who > gave us ideas for our Project Ideas [1] page, and a special thank

Re: object identity

I don't really have anything to add to this thread but I will say that Om's use of identical? is an implementation detail that's likely to change. = already does an identical? check, ideally Om could use not= in the future instead of (not (identical? ...)). David On Tue, Feb 25, 2014 at 12:54 PM

Re: Om: trouble with goog reference

Your markup needs to look something like: http://fb.me/react-0.9.0.js";> goog.require("om_ho.core"); HTH, David On Thu, Feb 27, 2014 at 6:26 AM, cig wrote: > Hi David > > I tried changing :advanced mode to :whitespace mode. My index.html file > looks as follows: > > > > >

Re: Om: trouble with goog reference

ally, afaik, the only > change was the id of the div (from "app" to "registry"). > > I'm having a lot of fun working on this stuff, btw. Om is very cool. > Looking forward to getting into the intermediate tutorial with Datomic too > :) > > ,chris > &

Re: Found some unexpected behavior to me

Fixed in 1.6. David On Thu, Feb 27, 2014 at 3:50 PM, Brent Millare wrote: > Clojure 1.5.1 > > user=> (defprotocol IEmit (-emit [x])) > IEmit > > user=> (defrecord css [y] IEmit (-emit [_] y)) > user.css > > user=> (-emit (->css 3)) > 3 > > user=> (map -emit [(->css 3)]) > IllegalArgumentExcepti

Re: Solving allocation problems; code review and core.logic

I'm cross posting this to the miniKanren mailing list. It sounds like core.logic or cKanren could be applied to your problem but would need more details. I also wouldn't rule out finite domain solvers like JaCoP. David On Wed, Mar 5, 2014 at 9:52 AM, Laurens Van Houtven <_...@lvh.cc> wrote: >

ANN: Om 0.5.2, Regeant, Quiescent, React interop & more

While I think Om's approach to application state management delivers considerable benefit, I think it would be unfortunate if all the labor put into reusable Om components was confined to Om users. With the latest release I've included examples demonstrating how two important things are now possibl

Re: [ClojureScript] Re: Test G.Closure lib release 0.0-20140226-71326067

Andrew, I've tried the new JARs on a couple of projects and I have not encountered these issues. Did you make sure to run a `lein cljsbuild clean`? Thanks. David On Wed, Mar 12, 2014 at 8:19 PM, Andrew Keedle wrote: > Stuart, > Did you ever get any response to this? I made the changes as sug

CLJS Advanced Compilation & JS Libraries lacking externs

I've written up an explanation how to make this work http://swannodette.github.io/2014/03/14/externs-got-you-down/ 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 fro

Re: [GSoC] Mentor for self-hosting ClojureScript compiler project?

Max, Just a fair bit of warning that such a project should probably only happen under GSoC only if it actually pushes along *official* support for bootstrapping ClojureScript in ClojureScript. Just forking the compiler and making changes until "it works" just isn't going to fly and I do not think

Re: Clojure 1.6.0-RC1 - LAST CHANCE, PLEASE TEST

Just tried 1.6.0-RC1 with ClojureScript master. All ClojureScript tests pass except for one which is due to assumptions about print order (different now due to hash code changes). Easy enough to fix once 1.6.0 actually ships. David On Tue, Mar 18, 2014 at 1:44 PM, Alex Miller wrote: > Thanks M

Re: Clojure 1.6.0-RC1 - LAST CHANCE, PLEASE TEST

Yep, we'll get rid of it once 1.6.0 actually ships. David On Tue, Mar 18, 2014 at 5:04 PM, Alex Miller wrote: > I assume that fixing this is a matter of updating src/clj/cljs/core.clj in > clojurescript to exclude unsigned-bit-shift-right? > > > On Tuesday, March 18, 2014 2:52:03 PM UTC-5, Amb

Re: om component state

On Thu, Mar 20, 2014 at 5:57 AM, Adrian Miron wrote: > > I'm starting to use om in some projects and one of the first components I > had to build was a simple notification component. It shows a message at the > top of the page. Other components in the page will use it to display > messages when er

Re: rant / cljs in cljs ? :-)

Unless you're compiling a very large file - with auto :optimizations :none you should always get sub-second compile times under auto. David On Fri, Mar 21, 2014 at 10:55 AM, Timothy Baldridge wrote: > are you using "lein cljsbuild auto" ? That's what I use, and I get about > 1-3 sec recompile t

Re: om component state

On Fri, Mar 21, 2014 at 11:45 AM, Adrian Miron wrote: > > > On Thursday, March 20, 2014 10:58:08 PM UTC+2, David Nolen wrote: >> >> >> If you don't pass app state data to this component then you don't need to >> bother with build at all. If you need a c

ANNN: ClojureScript 0.0-2197

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2197 Leiningen dependency information: [org.clojure/clojurescript "0.0-2197"] Changes & Enhancements: * updated Google Closure Li

Re: [ANN] Clojure 1.6

It looks like the zip file that usually included with the releases is missing? http://repo1.maven.org/maven2/org/clojure/clojure/1.5.1/ vs. http://repo1.maven.org/maven2/org/clojure/clojure/1.6.0/ Thanks, David On Tue, Mar 25, 2014 at 7:00 AM, Alex Miller wrote: > We are pleased to announce

Re: [ANN] Clojure 1.6

Thanks! On Mon, Mar 31, 2014 at 6:26 PM, Stuart Sierra wrote: > Oof, it's been ages since I looked at that stuff. I'll take a look. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.co

ANN: ClojureScript 0.0-2199

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2199 Leiningen dependency information: [org.clojure/clojurescript "0.0-2199"] The only difference is the removal of spurious warn

Re: om: state management considerations

On Wed, Apr 2, 2014 at 3:42 AM, rlewczuk wrote: > > First one is about object created by (om/build ...) - in all tutorials > these objects are always created on the fly in (render ...) functions. So > if some component disappears from view for some time, it loses its state. > This might be the ca

ANN: ClojureScript 0.0-2202

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2202 Leiningen dependency information: [org.clojure/clojurescript "0.0-2202"] This release is similar to 0.0-2199, it just addres

Re: A thought on Om/React

React is already headed in the direction you suggest. Still there would be advantages to having something native in Clojure of course and perhaps someone feels inclined to pursue that. On Tuesday, April 8, 2014, Dave Sann wrote: > I haven't built anything with OM or react as yet. But I have read

Re: Om and core.async: Necessary together?

It's mostly for demonstration purposes, but I think it will be a common pattern when more complex coordination is required. I think components should probably communicate via callbacks and applications can glue things together with core.async if it's beneficial. David On Wed, Apr 9, 2014 at 10:5

Re: Om and core.async: Necessary together?

gt; would be more beneficial to use callbacks or channels? Are there > 'rules-of-thumb' that I could follow until that intuition is established? > > > On Wednesday, April 9, 2014 8:40:19 AM UTC-7, David Nolen wrote: > >> It's mostly for demonstration purposes, but

Re: Om and core.async: Necessary together?

Also don't use a channel unless you actually need complex coordination. I would always default to a callback first. David On Wed, Apr 9, 2014 at 7:56 PM, David Nolen wrote: > Reusable components - use callbacks > Application components (non-reusable or less re-usable) - use channel

Re: Om and core.async: Necessary together?

the reusability issues over the last > week, so maybe I just need to wait until you write up your ideas. I really > want to figure this out and use it on a non-trivial real-world project (the > one I mentioned above). So if you need a lab rat for some of these > ideas... > > &g

ANN: Om 0.6.1, moving towards independently addressable components

Om 0.6.1 significantly changes how component local state works - we now rely on React's forceUpdate to update components that use local state. This is a significant change so I would like people test this out on their existing code bases as soon as possible. The immediate benefit is that component

Re: Core.logic appendo for string?

There's no easy way to do this beyond making your own relational string type as you've suggested. On Sunday, May 4, 2014, Adam Saleh wrote: > Hi, > > every once in a while I am toying with an idea of doing string > manipulation in core.logic. > > Naively trying to use appendo doesn't really work

Re: Clojurescript set count returning erroneous values.

Can you demonstrate a complete minimal example? Thanks, David On Tue, May 20, 2014 at 4:06 AM, Austin Haas wrote: > I'm having trouble isolating a small test case. I call the following code > in an update tick: > > (let [prev' @prev > state' @state] > (let [rems (clojure.set/differenc

ANN: ClojureScript 0.0-2227

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2227 Leiningen dependency information: [org.clojure/clojurescript "0.0-2227"] Enhancements * optimized case * CLJS-8

Re: core.match incorrect docstring?

Thanks for the report, docstring updated. David On Tue, May 27, 2014 at 5:16 PM, Dom Kiva-Meyer wrote: > The clojure.core.match/match docstring states that it takes "...a vector > of occurrences, vars. Clause question-answer syntax is like `cond`. > Questions must be wrapped in a vector..." >

Re: Clojure on iOS devices - Swift as a host?

I wouldn't pass judgement on Swift too soon. Eval works just fine in the REPL and it appears the language supports hot code loads out of the box. Swift also has real support for final fields via 'let'. I personally think a ClojureSwift could be quite interesting :) On Wednesday, June 4, 2014, Timo

ClojureScript & Clojure 1.6.0

Future releases of ClojureScript will have a hard dependency on Clojure 1.6.0. If you have any objections, speak up now :) 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 p

Re: ClojureScript & Clojure 1.6.0

ous what are the motivating factors? Are there > any new features/bug-fixes planned for ClojureScript that will depend on > Clojure 1.6.0 features? or is this just a case of keeping things as > up-to-date as possible? > > > On Friday, June 6, 2014 at 17:43, David Nolen w

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

;> >> On 06 Jun 2014, at 19:22, Andrey Antukh wrote: >> >> +1 >> >> >> 2014-06-06 19:19 GMT+02:00 Karsten Schmidt : >> >>> +1 >>> On 6 Jun 2014 16:59, "David Nolen" wrote: >>> >>>> Clojure 1.6.0 introd

Re: ClojureScript & Clojure 1.6.0

ching Socks wrote: > > Can a lein-cljsbuild clj+cljs project specify separate versions of Clojure > for the cljs and clj parts? > > If not, please give it another 6 months. > > > On Friday, June 6, 2014 10:43:42 AM UTC-4, David Nolen wrote: >> >> Future releases of

Re: ClojureScript & Clojure 1.6.0

> > > On Saturday, June 7, 2014 at 4:16, David Nolen wrote: > > > Given the feedback so far such a request seems to be in the minority. > You could run a separate project for the CLJS parts. That said, is there > something in the latest release (0.0-2227) that you f

Re: ClojureScript & Clojure 1.6.0

your local Maven. Use this in version number in your project. David On Fri, Jun 6, 2014 at 10:43 AM, David Nolen wrote: > Future releases of ClojureScript will have a hard dependency on Clojure > 1.6.0. If you have any objections, speak up now :) > > David > -- You receiv

Re: ClojureScript & Clojure 1.6.0

hash collisions in large 3d meshes as a result. Awesome! > > K. > > On 8 Jun 2014 18:07, "David Nolen" wrote: >> >> 1.6.0 branch is ready to be tested >> http://github.com/clojure/clojurescript/tree/1.6.0, please give it a try in >> your projects. You

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

orManager > println > WARNING: > /Users/viebel/libs/klozzer/target/cljsbuild-compiler-0/cljs/core/async/impl/ioc_helpers.js:353: > WARNING - unreachable code > {return null; > ^ > > Jun 10, 2014 7:49:49 AM com.google.javascript.jscomp.LoggerErrorManager > printSummary > WA

Re: solving an equation for all solutions with constraints: core.logic.fd

That's that's the suggested way - just pick a large bound. David On Tue, Jun 10, 2014 at 11:28 AM, cej38 wrote: > I found the solution to my first problem at > https://github.com/clojure/core.logic/wiki/Features (with a few small > changes by me): > > (run* [q] > (fresh [x y] > (fd/in x y

Re: solving an equation for all solutions with constraints: core.logic.fd

core.logic only currently supports solving finite domains CLP(FD), you'll have to look elsewhere for a CLP(R) solver for now. David On Tue, Jun 10, 2014 at 5:30 PM, cej38 wrote: > I picked a toy problem that was really easy to solve, figuring that once I > had the idea down, I would be able to e

ANN: ClojureScript 0.0-2234

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-2234 Leiningen dependency information: [org.clojure/clojurescript "0.0-2234"] This release fixes a critical bug around the `case`

Re: ClojureScript ^:export defprotocol

On iOS is advanced compilation really necessary? :simple + :static-fns true should suffice. On Wednesday, June 18, 2014, Mike Fikes wrote: > Is there a way to indicate that a (ClojureScript) protocol is intended to > be used from the host? > > Details: > > I can define a protocol and an implemen

ANN: ClojureScript 0.0-1885 (Source maps!)

ClojureScript, the Clojure compiler that emits JavaScript source code. The biggest change in this release thanks to Sean Grove - much improved source maps. You can provide a :source-map option to the compiler to name the source map file. Feedback on this significant enhancement welcome. README an

Re: ANN: ClojureScript 0.0-1885 (Source maps!)

1889 released, all changes are to make it easier to test the source map functionality. I've blogged some basic instructions here http://swannodette.github.io/2013/09/15/source-maps/ Feedback welcome! On Sun, Sep 15, 2013 at 2:48 PM, David Nolen wrote: > ClojureScript, the Clojure

Re: ANN: ClojureScript 0.0-1885 (Source maps!)

subscribed to that issue on Jira for a > while now, and here it is, alive and working! Just ran some demo code and > it looks amazing! Thanks Sean Grove and thanks David Nolen. I'll let you > know about any bugs I find. > On Sunday, September 15, 2013 2:48:46 PM UTC-4, David Nolen

Re: [ClojureScript] ANN: ClojureScript 0.0-1885 (Source maps!)

Use goog.string.format. David On Mon, Sep 16, 2013 at 11:35 AM, Joe Smith wrote: > I see that clojure.core/format is gone. Is there a replacement/alternative? > > --- > Joseph Smith > j...@uwcreations.com > @solussd > > > > > > > On Sep 16, 2013, at

Re: Weird core.async/ClojureScript not workings...

Which versions of ClojureScript and core.async are you using? David On Mon, Sep 16, 2013 at 5:25 PM, David Pollak wrote: > Howdy, > > I'm using core.async and ClojureScript and it seems that inside a go > block, if/when/loop/while code is never executed. > > For example: > > (def dog33 (go (

Re: Weird core.async/ClojureScript not workings...

sbuild "0.3.2"]] > > > On Mon, Sep 16, 2013 at 3:32 PM, David Nolen wrote: > >> Which versions of ClojureScript and core.async are you using? >> >> David >> >> >> On Mon, Sep 16, 2013 at 5:25 PM, David Pollak < >> feeder.of.the.be...@g

Re: Weird core.async/ClojureScript not workings...

- cljsbuild 0.3.3 > - prismatic 0.1.2 > > but they don't seem to cause issues with 1859. If you've got any tips on > using core.async master (maybe using lein's checkout feature?) I wouldn't > mind trying that. > > On Sep 16, 2013, at 3:32 PM, David Nolen wr

ANN: core.match 0.2.0-rc6

I believe this release finally eliminates all the remaining bugs around AOT. Will likely be the final release candidate. http://github.com/clojure/core.match Feedback welcome! David -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to thi

Re: GSoC Report: Expresso, symbolic manipulation of Algebraic Expressions in clojure

Impressive work congrats! On Mon, Sep 23, 2013 at 11:38 AM, Maik Schünemann wrote: > GSoC ends today and I can announce the 0.2.0 version of the expresso [1] > library. > It is build on top of core.logic and core.matrix and provides symbolic > manipulation of algebraic expressions. > > What's t

ANN: ClojureScript 0.0-1909

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-1909 Leiningen dependency information: [org.clojure/clojurescript "0.0-1909"] *Breaking Changes: * * Bump data.json to 0.2.3 and

Re: ANN: ClojureScript 0.0-1909

Oops bumping data.json and tools.reader are not breaking changes! :) On Fri, Sep 27, 2013 at 1:00 PM, David Nolen wrote: > ClojureScript, the Clojure compiler that emits JavaScript source code. > > README and source code: https://github.com/clojure/clojurescript > > New relea

ANN: core.match 0.2.0

No change since the last release candidate. http://github.com/clojure/core.match Have fun! 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

Re: [ANN] cljsfiddle.net

Wow, awesome. Yes to core.async support, there was a release yesterday with new goodies for Clojure and ClojureScript. David On Sat, Sep 28, 2013 at 6:24 AM, Jonas wrote: > Hi > > I’m working on a ClojureScript playground application ( > http://cljsfiddle.net) similar to jsfiddle[1], jsbin[2]

Re: [ANN] cljsfiddle.net

Just gave it a spin http://cljsfiddle.net/fiddle/swannodette.test-logic Great work. Is there anyway to turn on parentheses matching on in CodeMirror? Even better if Code Mirror can highlight unbalanced parens. (Using it also makes me realize that ClojureScript should really provide a way to colle

ANN: ClojureScript 0.0-1913

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-1913 Leiningen dependency information: [org.clojure/clojurescript "0.0-1913"] *Enhancements: * * Under incremental compilation re

Re: Question about vector-of

Not that I'm aware of. On Thursday, October 10, 2013, Mark Engelberg wrote: > (def a (conj (vector-of :long) 1 2 3) > (inc (a 1)) > > Is Clojure smart enough to figure out that (a 1) is a primitive long and > call the fast primitive version of inc? > > -- > -- > You received this message because

Re: core.match on a set

There's currently no support for matching sets and I have no plans in the near future. Patch welcome, it could be matched and optimized similarly to map matching. On Thursday, October 10, 2013, Phillip Lord wrote: > > I've been playing with core.match recently. One thing that I am confused > abou

Re: Question about vector-of

k in function headers. Is > that correct? > > Thanks, > > Mark > > > > > > On Thu, Oct 10, 2013 at 5:09 AM, David Nolen wrote: > >> Not that I'm aware of. >> >> >> On Thursday, October 10, 2013, Mark Engelberg wrote: >> >>

Re: Question about vector-of

> > Thanks, > > Mark > > > > > > On Thu, Oct 10, 2013 at 5:09 AM, David Nolen wrote: > >> Not that I'm aware of. >> >> >> On Thursday, October 10, 2013, Mark Engelberg wrote: >> >>> (def a (conj (vector-of :long) 1 2 3) >

Re: core.match on a set

k, and see if I can offer a patch, though. > > Phil > > David Nolen > writes: > > > There's currently no support for matching sets and I have no plans in the > > near future. Patch welcome, it could be matched and optimized similarly > to > >

ANN: ClojureScript 0.0-1933

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-1933 Leiningen dependency information: [org.clojure/clojurescript "0.0-1933"] Changes: * / in symbol now always delimits a namesp

ANN: ClojureScript 0.0-1934

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-1934 Leiningen dependency information: [org.clojure/clojurescript "0.0-1934"] The only change in this release - eliminating spuri

Re: No such namespace warning with Clojurescript repl

You can no longer use foo/bar to access properties, a slash now always indicates a namespace with CLJS 1933 and up. On Sat, Oct 19, 2013 at 12:47 PM, Greg Chapman wrote: > I've been working through the Clojurescript tutorial here: > https://github.com/magomimmo/modern-cljs > > When compiling ste

Re: ANN: core.match 0.2.0

If there's something specific you would like to see based on what is already present I'm listening. David On Fri, Oct 18, 2013 at 11:49 AM, François De Serres < francois.de.ser...@gmail.com> wrote: > Hi David, > > any chance to see core.match expose its compiler in the near future? > The abilit

Re: Request for help optimising a Clojure program

I note that the Clojure version isn't being given 12gigs of RAM, is this something you're giving to the JVM after when you run a AOTed version of the Clojure code. You also haven't said whether the timings for the smaller problems are significantly different between Scala and Clojure. David On

Re: Request for help optimising a Clojure program

On Tue, Oct 22, 2013 at 3:11 PM, Paul Butcher wrote: > Yeah - I have tried giving it more RAM without any effect on the timing > whatsoever. And I couldn't see the point of stopping people with less RAM > than that from being able to run it :-) > But without enough RAM most JVMs will thrash in G

Re: Request for help optimising a Clojure program

Those numbers make the larger problem runtime suspect. How are you running the Clojure version? With Lein? On Wednesday, October 23, 2013, Paul Butcher wrote: > On 22 Oct 2013, at 20:20, David Nolen > > > wrote: > > On Tue, Oct 22, 2013 at 3:11 PM, Paul Butcher > > >

Re: Request for help optimising a Clojure program

Lein doesn't use your specified JVM settings, you must override with ^:replace. It's also a good idea to set "-server" as Lein does not default to this. On Wednesday, October 23, 2013, Paul Butcher wrote: > On 23 Oct 2013, at 12:21, David Nolen > > > wrote: &

Re: Request for help optimising a Clojure program

If set construction was 1000X worse why don't the smaller problem sizes exhibit exactly the same issue? If the Scala version requires 12G why is the Clojure version steady at 300M? Aren't Scala for comprehensions optimized now into lower level loops? Clojure for comprehensions generate lazy sequen

Re: Request for help optimising a Clojure program

The Scala code is using immutable sets. On Wednesday, October 23, 2013, Timothy Baldridge wrote: > From what I can tell, Clojure uses persistent hash sets inside of set. > This can be fixed by replacing set with (into #{} data). Into uses > transients internally and should be much faster. > > I d

Re: Request for help optimising a Clojure program

The problem here is that you're not following your Scala solution closely enough. I suspect if you used defrecords to represent the pieces the way that you used a class in Scala you can avoid the number of collisions for larger problems. Not tested much but I tried something like the following and

Re: Request for help optimising a Clojure program

OK, it appears defrecord suffers from a problem that used to plague Scala case classes as well - http://issues.scala-lang.org/browse/SI-2537. David On Thu, Oct 24, 2013 at 8:08 AM, Paul Butcher wrote: > On 23 Oct 2013, at 18:37, David Nolen wrote: > > The problem here is that y

Re: Request for help optimising a Clojure program

What I suggested is far, far more conservative than anything else proposed on this or on the dev thread. Changing the hash implementation of sets and vectors etc. is likely to have unintended consequences for performance - http://www.scala-lang.org/old/node/8510.html The original Scala code used

ANN: ClojureScript 0.0-1978

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript New release version: 0.0-1978 Leiningen dependency information: [org.clojure/clojurescript "0.0-1978"] Changes: * tools.reader 0.7.10 Enhancements: * Sig

<    3   4   5   6   7   8   9   10   11   12   >