Thanks everyone - I was leaning towards maps and sounds like that's the
preferred approach.
On 26 April 2014 10:59, Gary Trakhman gary.trakh...@gmail.com wrote:
If it's more than a few parameters, I prefer maps.. It enables the
possibility of things like merge.
On Fri, Apr 25, 2014 at
thanks!
On 26 Apr 2014, at 03:18, Colin Jones trptco...@gmail.com wrote:
Since these projects have to be named lein-template, you can actually get the
full list via `lein search`, provided you don't need to search
non-standard/private repositories.
I bumped my :user profile's
While reading the clojure.java.jdbc code yesterday, I discovered to my
surprise that map destructuring can be used after an in an arglist.
This should give you all the described benefits of the two approaches you
mention
((fn [a {:as d}] d) 1 :opt1 'blah :opt2 false)
You can also do
Hi Paul,
Do you mind outlining the method you used? I am exactly looking for the
same. My Java skills are pathetic too.
Thanks,
Kras
On Wednesday, September 9, 2009 4:17:07 AM UTC+5:30, Paul Henning wrote:
Thanks for the information. Once I bit the bullet and learned a bit
of Java, it
Yes, that's the preferred way of accepting kwargs now, I think. But it's
just prettier syntax around the same problem. Note that using this form
doesn't accept an explicit map, I still have to place the params inline in
the function invocation. If I have:
(defn test1 [ {:keys [param1 param2] :as
Simpler yet using metadata:
(ns example.ppfn)
(defn print-pf [pf]
(if-let [ppf (::ppf (meta pf))] ppf pf))
(defmacro partial* [ args]
`(let [m# (pr-str '(partial* ~@args))
pf# (with-meta (partial ~@args) {::ppf m#})]
(defmethod print-method (class pf#) [o# w#] (print-simple
I haven't touched this project in a while, but it might be useful.
https://github.com/blancas/tinypost
This file has the relevant interop code:
src/main/clojure/blancas/tinypost/scan.clj
On Saturday, April 26, 2014 3:04:50 AM UTC-7, Kranthi Rajoli wrote:
Hi Paul,
Do you mind outlining the
If you use a ClojureWerkz project or two please read this announcement:
http://blog.clojurewerkz.org/blog/2014/04/26/major-breaking-public-api-changes-coming-in-our-projects/
--
MK
http://github.com/michaelklishin
http://twitter.com/michaelklishin
--
You received this message because you are
Neocons [1] is an idiomatic Clojure client for the Neo4J REST API.
3.0 has a *major breaking API change*.
Release notes:
http://blog.clojurewerkz.org/blog/2014/04/26/neocons-3-dot-0-0-rc1-is-released/
Background:
Elastisch [1] is a small, feature complete Clojure client for ElasticSearch
that supports both REST and native transports.
2.0 has one major breaking API change and is packed with improvements
related to ElasticSearch 1.0 and 1.1 releases.
Release notes:
added an issue at
http://dev.clojure.org/jira/browse/CMEMOIZE-14
On Thursday, April 24, 2014 6:42:08 PM UTC+3, Daniel Slutsky wrote:
Dear Clojure group,
I am running into an interesting issue with clojure.core.memoize.
I created a simple project depending on clojure.core.memoize.
Hello to all,
*Short version :* I think Clojure needs a documentation system in Clojure,
I would like to know if some efforts exist in that direction, and I am
willing to create it / contribute to it.
*Long version :*
I've been thinking for a while that the Clojure community could benefit a
Regarding the lein-templates for cljs going from very minimal to batteries
included, my personal opinion is that we should be able to create something like
http://yeoman.io/index.html
Any thoughts?
Thanks
mimmo
On 26 Apr 2014, at 00:49, Mark Engelberg mark.engelb...@gmail.com wrote:
Is
Greg's is a nice and clean solution for the data visualization problem,
assuming you're only going to use partials.
I hacked together a solution to support functions with equality semantics,
if anyone is interested. It doesn't support anonymous functions or
closures, but doing that would
This is a lovely idea.
I think prismatic schema is one well-accepted way to document data shapes,
but it's expected to be used inline. It would be nice to have flexibility
in what description systems are used in addition to flexibility of where
the docs live.
I agree that being able to see and
Personally, I like documentation in the same place as the code it
documents And I'd love to have the tests in the same file as well.
In both cases, I think the things are highly coupled by their nature, and
therefore I want them together (OK, tests aren't always - in the cases they
aren't,
Fair points. Well, leaving the possibility to document the code from just
anywhere is what I had in mind.
Le samedi 26 avril 2014 22:52:41 UTC+2, Jason Felice a écrit :
Personally, I like documentation in the same place as the code it
documents And I'd love to have the tests in the same
Thanks a lot . i got it wrong in my cascalog query. Now it worked.
--
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 be patient with
Could it be that 0.6.1 doesn't trigger a re-render of a component when
just `:opts' has changed? I have a parent component with passes a
boolean (`:selected?') down to it's children in the `:opts'-map.
The parent-component's `render' is called, but the children's isn't anymore.
I understand that
Hey guys I have seen this...
http://f.cl.ly/items/2T2d340o0k0W2d44212G/clj2.gif
Now, I want to know... has anything developed since? Is it available to
all?
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
Some thoughts:
Having concise documentation in the same place as the code minimizes a
certain kind of work: I want my functions to be commented in the source
file so that someone reading it later (maybe me) will quickly understand
what they're supposed to do. If Clojure didn't have
21 matches
Mail list logo
