`partial` won't work here because you're partially applying *two*
arguments, `type` and the :idVe portion of the args. `partial` only
lets you override an *unbroken* sequence of args at the *beginning* of the
arglist.
For instance, (partial log "DEBUG" "default message") would work. To
Hello, it worked, but if I use
(debug "TEST" :id "something")
is getting ArityException Wrong number of args (3) passed to ...
Em terça-feira, 23 de fevereiro de 2016 15:36:46 UTC-3, Josh Tilles
escreveu:
>
> My guess is that what you're looking for is:
> (def debug #(log "DEBUG" % :idVE
Thanks Zach, I would love to do an unfair comparison between clojure and
nodejs :)
Gonna give it a spin
On Tuesday, February 23, 2016 at 5:09:50 PM UTC, Zach Tellman wrote:
>
> For what it's worth, Aleph will handle pipelined requests in parallel:
> https://github.com/ztellman/aleph.
>
> On
My guess is that what you're looking for is:
(def debug #(log "DEBUG" % :idVE "COM"))
(see "Anonymous function literal" under
http://clojure.org/reference/reader#_dispatch)
However, note that defining functions in a "point-free"-ish style in
Clojure has a downside with regard to metadata, in
As the author of said libraries, I'd love to see somebody pick them up during
GSoC and continue the work.
The reason why development seems to have stalled, is different for each library:
- tools.analyzer and tools.analyzer.jvm are pretty much done and stable, all
that's left to do is fixing a
Hello all,
I´m trying to do something like:
(defn log [type message & {:keys [id idVe] :or {id "LOCAL" idVe "END"}}]
(println (str id ": " type " -> " message "<- " idVe)))
(def debug (partial log "DEBUG" ?? :idVe "COM"))
Is there any way to do what I want? Pass arguments to log and
For what it's worth, Aleph will handle pipelined requests in
parallel: https://github.com/ztellman/aleph.
On Tuesday, February 23, 2016 at 4:46:23 AM UTC-8, Miguel Ping wrote:
>
> Thanks, thats what I eventually found out.
>
> On Tuesday, February 23, 2016 at 12:39:00 PM UTC, jonah wrote:
>>
>>
It may, however keep in mind that Clojure supports Java 1.6+ and Stream was
added in 1.8. That's not an impossible hurdle, but it might make sense to
make longer before hurdling it.
On Tuesday, February 23, 2016 at 11:03:55 AM UTC-6, 676c7...@gmail.com
wrote:
>
> Hello!
>
> For interoperation
Hello!
For interoperation with Java, Clojure’s seq supports the Iterable
interface directly, which means that all Java collections are
automatically seqable. seq also supports the CharSequence and
java.util.Map interfaces, and arrays too.
Would it make sense to have seq also support
Just wanted to jump in here and say that Thomas is correct. Plugging into
the CLJS compiler is probably not the right place to start. The CLJS
compiler is built for speed and as such is somewhat less modular than the
tools.analyzer/tools.emitter projects. So start there if you're looking to
build
Would not we want to "plug in" to the Clojure compiler?
Feels weird to plug-in to ClojureScript to generate, say, python code.
On Monday, February 22, 2016 at 6:52:43 PM UTC-5, Antonin Hildebrand wrote:
>
> I like the idea.
>
> I was thinking about a similar project. The goal would be to design
Thanks, thats what I eventually found out.
On Tuesday, February 23, 2016 at 12:39:00 PM UTC, jonah wrote:
>
> Hi Miguel- pipelining is essentially http keep alive. A very old jetty
> thread
>
>
> http://jetty.4.x6.nabble.com/HTTP-1-1-Request-Pipelining-handling-td18682.html
>
>
Hi Miguel- pipelining is essentially http keep alive. A very old jetty
thread
http://jetty.4.x6.nabble.com/HTTP-1-1-Request-Pipelining-handling-td18682.html
indicates that for simplicity jetty will execute subsequent requests on the
kept-alive socket serially.
Jonah
On Mon, Feb 22, 2016 at
The post-Python effect came up briefly in another Conj talk -- in 2015 --
given by Elena Machkasova and two students, one of whom had had Clojure
first and the other Python. Their school offered it either way.
https://www.youtube.com/watch?v=n0yN1GauxCA
--
You received this message because
14 matches
Mail list logo
