How does this compare to Lacinia?
On Monday, 24 April 2017 11:24:22 UTC-7, Lei wrote:
>
> graphql-clj is a Clojure library that provides GraphQL implementation.
>
> In this new version 0.2.0, schema and query validator have been
> completely rewritten for simplicity and robustness. APIs have
I'll write more in an introductory blog post in a day or two. Until that,
there is a website http://clojurecuda.uncomplicate.org, that has the
details and documentation.
It is similar to ClojureCL (http://clojurecl.uncomplicate.org), but is
targeted to CUDA and Nvidia GPUs specifically. The
Unless prevented by outside considerations, it might also be
cleaner/simpler to copy all inputs from Java -> Clojure, do all the
algorithm work in Clojure, then copy all outputs back from Clojure -> Java.
I'm looking specifically at `java-memory-map`, but would also replace
native java stuff like
Having not gone through your code in detail, I would suggest replacing
`map` -> `mapv` to make it an eager operation so that state updates (i.e. `
next-states`) occur right away. The presence of laziness where it is not
needed or expected (especially in Java interop code) can cause problems
with
graphql-clj is a Clojure library that provides GraphQL implementation.
In this new version 0.2.0, schema and query validator have been completely
rewritten for simplicity and robustness. APIs have simplified in this new
version as well.
The github repository is:
Both, actually. The algorithm incrementally builds a tree via simulation.
There's a step of traversing the current version of the tree to find a
leaf, which requires immutability, as I have to remember the path taken
(the path is generated via simulation, not by walking an existing tree
Hello,
Op vrijdag 21 april 2017 23:08:22 UTC+2 schreef Alex Miller:
>
> The following bits of Clojure infrastructure are now https-only and
> redirect all traffic from http to https:
>
> https://build.clojure.org - Jenkins
> https://dev.clojure.org/jira - JIRA
> https://dev.clojure.org -
