Thanks for your feedback, Dylan!
If you define routes with :path and :query, will the route match/unmatch
> with undefined query keys? If so, how are they handled? If not, I'd suggest
> making query matching optional, where nils are substituted.
I'm not entirely sure what you mean, but I'll give
I doubt I can answer this as clearly as Rich or others but...
I think the answer to this lies in the fact that composing transducers is
composing reducer-transformers not reducer functions themselves.
When composing reducer-transformers, the result is another transformer.
When this new transfo
I'm also curious to understand how the underlying implementation of
transducers leads function composition to behave in the reverse order of
ordinary function composition.
On Thu, Aug 7, 2014 at 8:07 AM, wrote:
> Hello, what is the reason for comp to produce two different orderings
> depending
I just cut 0.0-2307, the only change is that the compiler now
optimizes anonymous multi-arity fns which results in a big performance
boost to transducer code.
David
On Thu, Aug 7, 2014 at 5:08 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> REA
I'm in agreement that Silk is a step in the right direction. I've reached out
to Dom and I think we can learn a lot from each other and work together to
improve the routing story in Clojure overall.
> There are some really good things in secretary. What do you think about them?
> Splat, regex,
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2301
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2301"]
The primary reason for this release is the inclusio
Just wanted to add that all of the current transducers work in Clojure
is now available in ClojureScript master.
David
On Wed, Aug 6, 2014 at 2:01 PM, Rich Hickey wrote:
> I pushed today the initial work on transducers. I describe transducers
> briefly in this blog post:
>
> http://blog.cognite
Ok, I got it. Instead of using transit-clj I can user the java library
directly. The reader automatically returns ArrayList and HashMap. Great!
On Thursday, August 7, 2014 8:11:50 PM UTC+2, Thomas Heller wrote:
>
> Both Transit and fressian take a Handler map as arguments to the
> reader/writer
Let me clarify. I removed the 'not-found' route and the api calls all
return an empty response.
--
Jonathon McKitrick
On Thu, Aug 7, 2014 at 3:14 PM, Jonathon McKitrick
wrote:
> Right, I tried removing that as well, and Friend still fails, and the api
> routes fail as well.
>
>
> --
> Jonath
Right, I tried removing that as well, and Friend still fails, and the api
routes fail as well.
--
Jonathon McKitrick
On Thu, Aug 7, 2014 at 2:54 PM, James Reeves wrote:
> Compojure routes are checked in order until one matches. You've set up
> your www-routes to match all possible routes, as
Compojure routes are checked in order until one matches. You've set up your
www-routes to match all possible routes, as you have a "catch-all"
not-found route at the bottom.
- James
On 7 August 2014 13:17, Jonathon McKitrick wrote:
> I'm serving up some html and js content, and using handler/s
Both Transit and fressian take a Handler map as arguments to the
reader/writer functions/constructors. So its pretty straightforward to
replace the default handlers with handlers that do what you want.
I have no example handy but it should be documented in both libraries.
Transit has something
I agree with Joel that I've found that secretary works very well with Om,
especially with a few abstractions built over it to built the corresponding
state. The opposite direction is tricky though, and the biggest problem I've
run into is that matching order is based on runtime route declaration
Hello, what is the reason for comp to produce two different orderings
depending on whether it composes partials or transducers?
(comp (partial filter even?) (partial map (partial + 1)))
(comp (filter even?) (map (partial + 1)))
Wouldn't it be more intuitive for upcoming clojurians to have both
Oh dear, I still haven't understood the blogpost on reducers yet, and
now there is this one as well.
Phil
Rich Hickey writes:
> I pushed today the initial work on transducers. I describe transducers briefly
> in this blog post:
>
> http://blog.cognitect.com/blog/2014/8/6/transducers-are-comin
Hi,
I have a program I wrote who needs to serialize java HashMaps and
ArrayLists to and from disk but AFAIK (and after some simple tests) it
seems fressian writes those maps/lists correctly but read them back as
clojure maps and lists (persistent).
Is there a way to tell fressian (could be tran
I'm serving up some html and js content, and using handler/site for that.
I have a separate handler/api group of routes under the "/api" context.
If I include the api routes before the site routes, the site works fine.
If the www routes come first, the api calls fail, probably because the
(ro
The integration with reducers is still todo.
On Aug 7, 2014, at 7:03 AM, Niels van Klaveren
wrote:
> Will the new transducer abstraction also (partly) replace / incorporate the
> reducer library ?
> So we could do something like (def xform (comp (fold +) (map inc) (filter
> even?))) to lever
I think it's sequencing. I'm going to try swapping the routes for api and
site.
On Thursday, August 7, 2014 7:19:33 AM UTC-4, Jonathon McKitrick wrote:
>
> So here's what I discovered:
>
> If I wrap ONLY the www-routes in Friend and remove api-routes entirely, it
> works. So far, I've tried se
So here's what I discovered:
If I wrap ONLY the www-routes in Friend and remove api-routes entirely, it
works. So far, I've tried several combinations of route, handler/api,
handler/site and friend and I get incorrect results, most often a null page.
Any ideas on how to wrap both handler/api a
Will the new transducer abstraction also (partly) replace / incorporate the
reducer library ?
So we could do something like (def xform (comp (fold +) (map inc) (filter
even?))) to leverage parallelism ?
On Wednesday, August 6, 2014 8:01:24 PM UTC+2, Rich Hickey wrote:
>
> I pushed today the ini
Thanks Rich!
Transducers, like all of your releases, are an eye opener.
I've always felt slightly hesitant to use core.async's version of sequence
functions, because of the overhead of intermediate channels. Then there was
the strictness tradeoff with reducers. All of that complexity, gone from m
Looks nice, although I still need to wrap my head arround it.
I don't believe in micro-benchmarks but I did one anyways cause I was
curious how transduce would stack up against reduce (not reducers).
https://github.com/thheller/transduce-bench
transduce
Evaluation count : 2220 in 60 samples of
23 matches
Mail list logo
