Have you considered adding an equivalent to lein’s pedantic option, i.e. an
option that would die on ambiguous versions rather than make a choice, thereby
forcing users to make that choice explicit as a top-level entry? (Or through
exclusions etc.)
As an aside, is it even possible on the JVM to
You could do it by “rooting” the package (aka change the package path).
Most JVM languages root their dependencies to avoid collisions with user
space dependencies. ASM is the most common Clojure does and I think Kotlin
and Scala do as well. I think Guavas murmur3 is rooted in Clojure as well
for t
It really boils down to understanding garbage collection: memory that cannot be
reached anymore is freed. In the first code sample, when running (last r), the
compiler has detected that r is never used afterwards, so it clears the local
variable. This means that while last is walking through the
Hi everybody,
I am using parkour to implement algorithms in the book "MapReduce Design
Patterns". Some of the algorithms make use of setup and cleanup methods. Is
there a way I can use them in parkour.
Thanks
--
You received this message because you are subscribed to the Google
Groups "Clo
On Monday, January 8, 2018 at 2:47:23 AM UTC-6, Gary Verhaegen wrote:
>
> Have you considered adding an equivalent to lein’s pedantic option, i.e.
> an option that would die on ambiguous versions rather than make a choice,
> thereby forcing users to make that choice explicit as a top-level entry
Hi All,
I'd like to announce the release of Pink 0.4.0 and Score 0.4.0:
[kunstmusik/pink "0.4.0"]
[kunstmusik/score "0.4.0"]
Pink is an audio engine library, and Score is a library for
higher-level music representations (e.g. notes, phrases, parts,
scores).
Change logs are available at:
https:
