This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (69)
- # babashka (21)
- # beginners (246)
- # calva (49)
- # chlorine-clover (19)
- # circleci (3)
- # clj-kondo (38)
- # cljsrn (1)
- # clojure (52)
- # clojure-australia (2)
- # clojure-europe (41)
- # clojure-nl (5)
- # clojure-spec (4)
- # clojure-taiwan (2)
- # clojure-uk (28)
- # clojurescript (12)
- # cryogen (6)
- # cursive (6)
- # datahike (3)
- # deps-new (5)
- # fulcro (2)
- # garden (1)
- # graalvm (3)
- # hoplon (48)
- # jackdaw (6)
- # jobs (3)
- # kaocha (6)
- # malli (3)
- # off-topic (51)
- # rdf (1)
- # reagent (40)
- # reitit (32)
- # remote-jobs (1)
- # reveal (24)
- # shadow-cljs (21)
- # startup-in-a-month (5)
- # xtdb (8)
Are you interested academically, or are you planning on any part of your system relying upon that likelihood of collision? Depending on your goals, I'd recommend trying to avoid relying upon that likelihood of collision.
I built a system on it being unique and now it looks like it collides pretty frequently in practice
Unless you are talking about UUID's or something, with so many bits that are uniformly distributed that you can prove miniscule probabilities of collision.
With 32 bits of hash result, if they were uniformly randomly distributed, the so-called birthday paradox predicts about a 50% chance of at least one collision if you get up to 2^16 = 65,536 of them.
I have no reason to think that
hash on Clojure functions is uniformly randomly distributed, though.
Oh wow, I missed that ClojureCLR now supports running on .Net Core, that's a big achievement. Seems everything works except AOT, and its up with Clojure 1.10 in featureset. https://groups.google.com/g/clojure-clr/c/MdxEbo0znAw
yup... i'm happy that there's an effort on this.. i tried the repl, it works fine so far... hope the rest (compilation, etc) will follow... definetly watching this space :-)
Ya, its been a while since I've used the .net ecosystem, but blazor and xamarin seem nice, and compilation to web assembly. So if ClojureCLR can get that working it could be interesting.
yup... i'm learning F# on the side also... in fact, i have both fsharp and clojure slack channels opened.. hehe.. i hope both communities interact more and share... there's bolero for F# (to do blazor stuff).. maybe clojureclr could leverage that as well
There's https://github.com/arcadia-unity/Arcadia but I think it might use its own clojureCLR fork
Well you can use interop with the .Net ecosystem, similar to Java interop for Clojure JVM I believe.
But I don't think ClojureCLR is widely used yet, so I haven't seen many Clojure based libs for it. I'd assume most lib that works for Cljs as well as Clojure would be easy enough to add support for ClojureCLR.
I don't think I have a leak because all my app's objects/classes get eventually GCed. But I'm not sure if it's intended usage to have so many classloaders around
can't remember the details but i think i remember that nrepl executions can result in new classloader objects. if you can compare against an instance using a socket server or just no repl at all you might see a large difference
Thanks for the pointer! It lead me to https://github.com/nrepl/nrepl/issues/8 which looks related, as I'm using
[org.clojure/tools.nrepl "0.2.13"] which predates that issue
(that dep is outdated, I know)
I am a bit confused to why I cannot use
var in this function:
(defn fname [f]
(-> f var meta :name))
I understand the reader macro would not work (since it would be quoting the literal symbol in that ns?) and guess that it is because
var is a special form that it fails, but why? Is the effect the same as if I would have used the reader macro?
var is a special form that works more like a macro than a function.
(var f) also tries to look up
f, not the value of
ns-resolve is very weird, but for whatever reason people always seem to grab that first rather than the simpler resolve
Perhaps because of the name places its api doc next to the other namespace functions, the main docs being in alphabetical order. Obviously there’s the cheatsheet nowadays.
I have a vector of functions (a middleware stack) and I want to make a simple tapper that
tap>s the context after each middleware, function name included, but maybe they have to be quoted to be resolvable?
I remember that someone was able to obtain a reasonable name from a function using a snippet they found in clojure's spec source code, but I can't seem to find it
yeah, resolve needs a symbol, clojure doesn't really encourage function / symbol cross translation
maybe it was:
(defn- fn-sym [^Object f] (let [[_ f-ns f-n] (re-matches #"(.*)\$(.*?)(__[0-9]+)?" (.. f getClass getName))] ;; check for anonymous function (when (not= "fn" f-n) (symbol (clojure.lang.Compiler/demunge f-ns) (clojure.lang.Compiler/demunge f-n)))))
IMHO you can kind of make that work, but there's likely a much simpler solution that doesn't require turning functions into symbols
eg. providing the var rather than the function in the place where the middleware is added
I should have linked to it earlier, but I found it using jump to source in my editor before I could find it on github
@love.lagerkvist You can also attach metadata to clojure functions, or keep a map of fn obj -> name
oh, that a hack worthy of its name. @borkdude I guess that would be the saner choice, considering the number of functions is quite small. There is also (de-)munge I guess, not sure about the characteristics of that, but it sorta does what I want.
(require '[clojure.main :as m]) ((fn [f] (-> f class str m/demunge)) util/qualified-keyed-ns-publics) ; => "class motform.bestå.util/qualified-keyed-ns-publics"
the authorities are working under design constraints that probably don't apply to your project