Hi, I really need help on my school clojure project, I have to be able to
do a "project1b" and add dataset, remove dataset, use dataset, save, quit,
summary, mean, median... etc to build a full stats system.
I got most of it and also most of the driver function but I can't seem to
build a
On Dec 20, 2015 7:20 PM, "Mike Rodriguez" wrote:
>
> The distinction between names is important when one is a predicate and
the other is not. However I think it would be more useful if it were
every-fn since it is often more useful to have the final return value vs
just true
Just putting CiderX through it's paces now. Reeeally great work man!!
Especially the debugging support, which just works.
The only thing I'm wondering, is if the debugger has:
- a *step into* function
- ability to set a break point in a 3rd party lib (where you can't put
*#break* or
Hi Min,
In your project
- Where does it come from? A database (you mentioned a driver), csv or
json file?
- What does the shape of the data look like in a Clojure runtime? Is
there some sample code or Clojure data structures we can look at?
Tim
On Mon, Dec 21, 2015 at 4:03 PM,
bouncer is a validation library for Clojure apps
Github: https://github.com/leonardoborges/bouncer
Clojars: https://clojars.org/bouncer
The main change with 1.0.0 is that all validators are now optional by
default. This fixes pre-existing API inconsistencies. bouncer now works
with
I'd say, same as you would destructure them inline: [& {:keys [k1 k2]}]
--
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
Hi,
A new version of the clj-nativedep library has been released to clojars.
The library provides a "standard" way to handle native library dependencies
and OS detection. This version adds support for explicit mac detection via
the (mac?) function.
See:
Hi,
Is there some formal syntax used by ^:arglists? I want to express
key-value pairs that are spliced, e.g. (some-fn :k1 value :k2 value)
Thanks,
Georgi
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to
Do you have an example where it would be more useful?
On Monday, December 21, 2015 at 2:20:41 AM UTC+1, Mike Rodriguez wrote:
>
> The distinction between names is important when one is a predicate and the
> other is not. However I think it would be more useful if it were every-fn
> since it is
Nice work! Thanks!
On Mon, Dec 21, 2015 at 11:15 AM, Leonardo Borges <
leonardoborges...@gmail.com> wrote:
> bouncer is a validation library for Clojure apps
>
>
> Github: https://github.com/leonardoborges/bouncer
> Clojars: https://clojars.org/bouncer
>
>
> The main change with 1.0.0 is that
I have downloaded Counterclockwise with integrated Eclipse IDE for Windows.
I start new project:
(ns newclojure.core)
(defn foo
"I don't do a whole lot."
[x]
(println x "Hello, World!"))
but when I try run appears window "Waiting to new REPL process to be ready"
and output in console is
After that message, a repl window should appear in which you can type and
evaluate clojure expressions.
After loading the repl, check how to:
- load current namespace into the repl and evaluate the functions in the
repl
- evaluate an expression on the workspace
I dont remember the shortcuts
Nothing specific but for the same reason you'd want to use 'and' in other
scenarios. You want the short-circuit behavior if certain criteria are met.
Only in this case you just want a function that does it instead.
One contrived example coming to mind:
(every-fn iterative-has-next? get-next)
Here are some functional programming job opportunities that were posted
recently:
Software Engineer (Scala/Play/Scala.js/React) at AdAgility
https://functionaljobs.com/jobs/8871-software-engineer-scala-play-scalajs-react-at-adagility
Cheers,
Sean Murphy
FunctionalJobs.com
--
You
I'd like the keys to be optional and destructuring does not support that.
On Mon, Dec 21, 2015, 3:48 PM Herwig Hochleitner
wrote:
> I'd say, same as you would destructure them inline: [& {:keys [k1 k2]}]
>
> --
> You received this message because you are subscribed to
It does. When not passed, a key is nil, or you can provide an or binding:
[& {:keys [k1 k2] :or {k1 :default1 k2 :default2}]
--
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
I found that
Org-mode version 8.3.2 and CIDER 0.11.0 snapshot (package: 20151212.1044)
works great and can be easily be installed from repos.
On Sunday, December 20, 2015 at 6:16:15 PM UTC+1, Johannes wrote:
>
> Thanks, for the explanations. I hope for the best, that there will be an
> working
err​ [& {:keys [k1 k2] :or {k1 :default1 k2 :default2}}]
--
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 your
first
18 matches
Mail list logo