A very cool of use of core.logic, look forward to seeing where it goes :)
On Wed, May 29, 2013 at 11:10 AM, Maik Schünemann wrote:
> Hello,
> I am glad to announce that my proposal got accepted for google summer of
> code.
> I am doing the algebraic expression project idea which could lay the
>
A core.logic cheatsheet would be a fantastic resource. I'd also welcome
help in generating the basic doc pages.
On Wed, May 29, 2013 at 1:08 PM, Benjamin Peter wrote:
> Hello,
>
> I am currently trying to find my way to using clojure core logic, watching
> some videos, reading tutorials and tryi
Good catch - please file a ticket here
http://dev.clojure.org/jira/browse/MATCH. Please attach any
work-in-progress patch you may have there and I'll review.
Before I can apply any work you've done you need to send in your
Contributor Agreement (CA) - http://clojure.org/contributing
Thanks,
David
request and fix/apply it when I've been added to the Clojure
> contributors.
>
>
>
> On Wed, May 29, 2013 at 12:36 PM, David Nolen wrote:
>
>> Good catch - please file a ticket here
>> http://dev.clojure.org/jira/browse/MATCH. Please attach any
>> work-in-pro
You might find this work in progress interesting then:
http://github.com/clojure/core.async
On Thu, May 30, 2013 at 3:46 PM, David Pollak wrote:
> Paul,
>
> Thanks... but I want the opposite of delay.
>
> Basically, I do not want to consume a thread waiting for a Future to be
> satisfied. I wan
I've looked at extractors a little bit, but I would need to investigate
further. Does this offer any more power than supporting arbitrary function
application in patterns?
Also, I'm unlikely to dive into any feature addition related issues until
all these pressing bugs in JIRA are squashed.
On T
That said feel free to add an enhancement ticket.
On Tue, Jun 4, 2013 at 5:12 PM, David Nolen wrote:
> I've looked at extractors a little bit, but I would need to investigate
> further. Does this offer any more power than supporting arbitrary function
> application in patterns?
Fixes:
-
* variadic aset
* CLJS-513: fix out bound behavior for vectors
* CLJS-515: emit positional factories for deftype
* IReduce for primitive arrays and lists
Changes:
-
* CLJS-499: ObjMap deprecated in favor of PersistentArrayMap
Enhancements:
-
* Added PersistentArrayMapSeq/KeyS
I'll try to repost that list on my new blog, in the mean time:
Art of Prolog
Concepts Techniques and Models of Computer Programming
Prolog Programming for Artificial Intelligence
The Reasoned Schemer
Are all all good starts.
On Sat, Jun 8, 2013 at 9:27 AM, Craig Ching wrote:
> I was looking f
Maybe this is an unintended side effect of the changes around unboxed
support in loop/recur?
On Thu, Jun 13, 2013 at 10:50 PM, Jason Wolfe wrote:
> Taking a step back, the core problem we're trying to solve is just to sum
> an array's values as quickly as in Java. (We really want to write a fan
At long last I've come around to overhauling core.match.
Changes/Fixes/Enhancements are documented here:
http://github.com/clojure/core.match/blob/master/CHANGES.md
core.match should no longer have AOT issues as far as I know and many long
outstanding bugs have been eliminated. The ClojureScript
CLP(Set) has not been implemented yet.
On Tue, Jun 18, 2013 at 2:36 AM, cig wrote:
> Is CLP(Set) for core.logic available for use?
> It does not seem like core.logic 0.8.3 contains this feature.
> How should I access it if it is available?
>
> --
> --
> You received this message because you are
e gone through some
> documentation on github by David Nolen. I am now trying to solve this
> problem: Anyone willing to do some practice can try and share the
> solution.
>
> *SOLVE THIS PROBLEM.*
>
> *The Diplomats at Muthaiga Estate*
>
> The facts essential to solving the probl
On Mon, Jun 17, 2013 at 1:04 AM, David Nolen wrote:
> At long last I've come around to overhauling core.match.
>
> Changes/Fixes/Enhancements are documented here:
> http://github.com/clojure/core.match/blob/master/CHANGES.md
>
> core.match should no longer have AOT issues as
No that was to illustrate an idealized solution not working code.
On Tue, Jun 18, 2013 at 1:47 PM, cig wrote:
> Hi David
>
> Did you not make use of it for solving this puzzle?
>
> https://gist.github.com/swannodette/5127150
>
>
> On Tuesday, 18 June 2013 13:38:48
Calling seq on vector returns a sequence which is no longer a vector. The
docstring is pretty specific about which types it's supposed to work on.
clojure.core/peek
([coll])
For a list or queue, same as first, for a vector, same as, but much
more efficient than, last. If the collection is empt
Using `def` like that is simply incorrect. `def` should always be at the
top level unlike say Scheme.
I would first remove all internal defs and then rerun your benchmarks.
On Fri, Jun 21, 2013 at 8:36 AM, Colin Yates wrote:
> Hi all,
>
> I am doing some (naive and trivial) performance tests b
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.
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
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
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
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
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 (
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
- 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
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
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
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
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
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
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]
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
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
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
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
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:
>>
>>
>
> 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)
>
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
> >
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
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
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
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
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
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
1 - 100 of 1520 matches
Mail list logo
