For serious ClojureScript scripting you should try http://planck-repl.org/
On Fri, Dec 9, 2016 at 7:46 AM, Asim Jalis wrote:
> I wrote a blog post on how to quickly get started with Clojure.
>
> How To Use Clojure For Scripting
> http://asimjalis.github.io/blog/2016/12/07/clojure-for-scripting.h
On Thursday, December 8, 2016 at 3:46:25 PM UTC-5, Asim Jalis wrote:
>
> I wrote a blog post on how to quickly get started with Clojure.
>
> How To Use Clojure For Scripting
> http://asimjalis.github.io/blog/2016/12/07/clojure-for-scripting.html
>
You might also look at [inlein](http://inlein.org/
REPL is "like doing engine repairs on a plane in flight." nice.
On Dec 8, 2016 2:46 PM, "Asim Jalis" wrote:
> I wrote a blog post on how to quickly get started with Clojure.
>
> How To Use Clojure For Scripting
> http://asimjalis.github.io/blog/2016/12/07/clojure-for-scripting.html
>
> --
> You
I wrote a blog post on how to quickly get started with Clojure.
How To Use Clojure For Scripting
http://asimjalis.github.io/blog/2016/12/07/clojure-for-scripting.html
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email t
Thanks Alex. I agree it probably isn't "needed", was just a little
surprised to discover the asymmetry. Mostly was curious if there was some
deeper design decision, e.g. that you need to start with some set of
primitive predicates upon which you can start building named specs.
On Thursday, Dece
In general, you shouldn't need to do this (it is better to attach the
generator to the spec). Generator mappings are provided for core Clojure
predicates so that many common predicates gen automatically and so that
they can be combined (via things like s/and) with other predicates that
filter b
Though one can obviously attach a custom generator to a keyword-named spec,
it appears there is no way to do the same for a custom predicate function.
I see that the generators for predicate functions testing for core
primitives are hard-coded in the private clojure.spec.gen\gen-builtins.
Curio
Would really help to have a minimal example of this without your macro
involved. I'm wondering if this is really same thing
as http://dev.clojure.org/jira/browse/CLJ-1403 in particular.
On Thursday, December 8, 2016 at 7:54:46 AM UTC-6, Justus Adam wrote:
>
> When executing `macro expand1()` wit
When executing `macro expand1()` with the compiler unresolvable symbols
aren't an issue, except if they are fully qualified and their corresponding
namespace does not exist, in which case a ClassNotFoundException is thrown.
I find this to be inconsistent behaviour, since unresolvable symbols
the
In that case you can use mapv:
(mapv
(fn [xs]
(mapv
(fn [x]
(if (= x "5")
"XX"
x))
xs))
players)
Two notes:
1. There is room for optimization if you only want to map one element. This
currently will just keep going. A smart implementation could ba
Is there a way to generalise?
I.e a function that allows you to swap any of the 1-9?
On Wednesday, 7 December 2016 18:06:19 UTC, Andy- wrote:
>
> One option is to use keep-indexed:
>
> (first
> (keep-indexed
> (fn [i xs]
> (first
> (keep-indexed
> (fn [j x]
>
Yep, I mentioned the Almanac to "senior stakeholders" while pitching the
book :)
It was a less internet-based age, but I think there is still room for an
offline reference.
Thanks
Renzo
On Thursday, 8 December 2016 07:05:07 UTC, Torsten Uhlmann wrote:
>
> Thanks for working on this!
>
> Back i
Thanks Ryan, added this (and Alex's) to the book issues tracker. Will land
in the following releases.
On Wednesday, 7 December 2016 23:43:28 UTC, Ryan Fowler wrote:
>
> I love the idea.
>
> A gotchas section of some sort could be useful. For instance, a detail
> about `case` to consider mention
Hey Alex, many good points and great feedback. More inline.
On Wednesday, 7 December 2016 22:57:07 UTC, Alex Miller wrote:
>
> This is a cool idea so thanks for working on it.
>
> I was going to buy this (as I buy most of the Clojure books that come out)
> but $48 for an unfinished ebook put me
14 matches
Mail list logo
