Hi,
I'm trying boot scripting capabilities so I have the following file:
#!/usr/bin/env boot
(set-env!
:dependencies '[[org.clojure/clojure "1.6.0"]])
(defn -main
[]
(println "before")
(for [s ["one" "two" "three"]]
(do
(spit "output" s :append true)
(println s)))
(print
For is lazy. Replace it with doseq.
Use doseq when you want side effects to occur and do not need
a result.
Luc P.
Sent from my iPhone
> On Jun 18, 2015, at 07:51, Haim Ashkenazi wrote:
>
> Hi,
>
> I'm trying boot scripting capabilities so I have the following file:
>
> #!/usr/bin/env boot
Btwy,
For is not a loop as in imperative languages. It returns a lazy sequence.
Luc P.
Sent from my iPhone
> On Jun 18, 2015, at 07:51, Haim Ashkenazi wrote:
>
> Hi,
>
> I'm trying boot scripting capabilities so I have the following file:
>
> #!/usr/bin/env boot
> (set-env!
> :dependencie
How is stuartsierra/component OOP when it is building an immutable object
graph? (Contrast that to Guava etc.)
On Thu, Jun 18, 2015 at 5:15 AM, Xiangtao Zhou wrote:
> hi guys,
>
> Constructing simple clojure project is trival, just make functions. if the
> project grows large, with more datasour
OOP does not mean mutab... erh... anything, really, but there is an
argument to be made for calling an immutable blob that carries data and the
operations to act on it an "immutable object". If every "mutative"
operation returns a modified copy of the object, you can have immutable OOP.
On Thursda
oop means object oriented programming, which doesn't mean mutable. record
is oop and immutable. when you use java, you can asume everthing is
immutable.
if i use dynamic to implement the object, i can test it with "binding";
others i can test with "with-redefs". so it works, except side effect
Could I suggest someone who wants a core.matrix integration simply does the
protocol implementation and submits it to Dragan as a PR?
On Thu, Jun 18, 2015 at 1:20 AM, Daniel wrote:
> Just another +1 to include a core.matrix implementation
>
> --
> You received this message because you are subscr
Dear CIDER Devs,
On Tuesday, June 16, 2015 at 4:33:48 PM UTC+2, Bozhidar Batsov wrote:
>
>
> CIDER 0.9 is finally out! You can read more about the release here
> http://batsov.com/articles/2015/06/16/cider-0-dot-9/
>
>
thanks for the time and effort you've put into this! Works fine for me.
Up
Happy to hear this! :-)
On 18 June 2015 at 14:36, Stefan Kamphausen wrote:
> Dear CIDER Devs,
>
>
> On Tuesday, June 16, 2015 at 4:33:48 PM UTC+2, Bozhidar Batsov wrote:
>>
>>
>> CIDER 0.9 is finally out! You can read more about the release here
>> http://batsov.com/articles/2015/06/16/cider-0-d
Thanks Luc,
This was a simplification if what I really have :) I actually need the
result. The actual code was something like:
(let [results (for [host hosts]
(future (remote-exec commands host)))]
(pmap deref results))
where remote-exec runs commands via ssh-clj.
Is there
pmap is still semi-lazy, and there's little point to derefing futures in
parallel.
You'd be better off with:
(doseq [r results]
(deref r))
Or:
(dorun (map deref results))
- James
On 18 June 2015 at 12:57, Haim Ashkenazi wrote:
> Thanks Luc,
>
> This was a simplification if wha
Thanks James, it works now :)
On Thu, Jun 18, 2015 at 3:04 PM, James Reeves wrote:
> pmap is still semi-lazy, and there's little point to derefing futures in
> parallel.
>
> You'd be better off with:
>
> (doseq [r results]
> (deref r))
>
> Or:
>
> (dorun (map deref results))
>
> -
By the way, I just tried connecting to two different repls from the
same project (the regular one + one started by fighweel) and it made
my Emacs hang :-\
Connecting to multiple repls on different projects works fine.
Thanks,
BG
On Thu, Jun 18, 2015 at 5:26 PM, Bozhidar Batsov wrote:
> Happy to
Submit a ticket + some repro steps and we'll have a look at it.
On 18 June 2015 at 15:55, Baishampayan Ghose wrote:
> By the way, I just tried connecting to two different repls from the
> same project (the regular one + one started by fighweel) and it made
> my Emacs hang :-\
>
> Connecting to m
Yeah, it usually happens when you start the second REPL while having the
REPL buffer open. It doesn't happen if you open the second REPL e. g. on
the project.clj...
On Thursday, June 18, 2015 at 2:56:12 PM UTC+2, Baishampayan Ghose wrote:
>
> By the way, I just tried connecting to two different
Oh and you can also C-g and kill the unusubal REPL buffer if this happens.
On Thursday, June 18, 2015 at 4:31:25 PM UTC+2, Leon Grapenthin wrote:
>
> Yeah, it usually happens when you start the second REPL while having the
> REPL buffer open. It doesn't happen if you open the second REPL e. g. on
On that note, the nrepl 0.2.6 problem is a pretty old issue by now. Does
anyone know if there are any plans to update leiningen.
On Wednesday, June 17, 2015 at 3:04:29 AM UTC-4, Isaac Zeng wrote:
> leiningen use org.clojure/tools.nrepl 0.2.6 cider-nrepl throw warning
>
> On Tuesday, June 16, 20
You should definitely collect all this information in a bug report and
we'll track this issue down.
On 18 June 2015 at 17:32, Leon Grapenthin wrote:
> Oh and you can also C-g and kill the unusubal REPL buffer if this happens.
>
>
> On Thursday, June 18, 2015 at 4:31:25 PM UTC+2, Leon Grapenthin
Hi!
I cannot figure out, what the difference between let and let* is. Can
anyone enlighten me?
Johannes
--
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 a
http://lmgtfy.com/?q=clojure+%22let+vs.+let*%22
--
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 post.
To
On Thursday, June 18, 2015 at 4:29:55 PM UTC-4, Johannes wrote:
>
> Hi!
>
> I cannot figure out, what the difference between let and let* is. Can
> anyone enlighten me?
>
Let is a macro that wraps let* and adds destructuring. There's a similar
relationship between fn and fn*, letfn and letfn*, a
thanks
Am Donnerstag, 18. Juni 2015 22:35:53 UTC+2 schrieb raould:
>
> http://lmgtfy.com/?q=clojure+%22let+vs.+let*%22
>
--
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 fr
Basically you the user should not worry about the starred versions
On Thu, Jun 18, 2015 at 1:40 PM Johannes wrote:
> thanks
>
> Am Donnerstag, 18. Juni 2015 22:35:53 UTC+2 schrieb raould:
>>
>> http://lmgtfy.com/?q=clojure+%22let+vs.+let*%22
>>
> --
> You received this message because you are s
http://jafingerhut.github.io
I'm jumping the gun a little bit by announcing this, as the links for the
new Clojure 1.7.0 vars like update, run!, dedupe, etc. do not link to any
place useful on ClojureDocs.org or Grimoire yet, but I am guessing they
will in not too long from now, when those sit
Am Mittwoch, 3. Juni 2015 11:05:03 UTC+9 schrieb Alex Miller:
>
> Try pr with 1.7.0-RC1 ...
Meh:
user=> (def bla 4)
#'user/bla
user=> (pr-str #'bla)
"#'user/bla"
user=> (edn/read-string (pr-str #'bla))
RuntimeException No dispatch macro for: '
clojure.lang.Util.runtimeException (Util.java:221
In common lisp, 'let' didn't evaluate it's bindings in any guaranteed order
(well, it is specified as being evaluated in parallel), however, 'let*'
evaluated it's bindings in order from left to right.
This enabled you to use the sequentially previous bindings in the
evaluation of later bindings
I mean, as long as that's the only case, it's fine. But I don't know what
cases there are…
--
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 -
There are plenty of votes for a core.matrix wrapper to this great project,
but I'll add one point. I came to Clojure from Common Lisp. I had a
neural network application in Common Lisp that didn't use matrices, and I
decided I needed to rewrite it from scratch using matrices. Common Lisp
ha
28 matches
Mail list logo
