Fork me on GitHub

If i always refer to a java class with its fully qualified name, do i still need to add it to ns :import declarations ?

Alex Miller (Clojure team)00:08:36

import just lets you refer to it unqualified

👍 1

IIRC :import had some extra nuance relative to static class initializers, I can be wrong though

Alex Miller (Clojure team)12:08:09

no, import does not load the class

Alex Miller (Clojure team)12:08:32

it just updates the namespace mappings


is there a way of type hinting proxy-super? On this code and `*warn-on-reflection*`:

(proxy [javafx.scene.control.ListCell] []
    (updateItem [item empty?]
      (proxy-super updateItem item empty?)
I'm getting call to method updateItem can't be resolved (target class is unknown).


damn, thanks!


hmm but doesn't work on my case :thinking_face:


oh yeah, that may be it


@U2FRKM4TW out of curiosity, what was your approach for finding that comment?


Full text search for proxy-super in one of my projects that has a lot of dependencies. :)


oh nice, didn't knew about it. Thanks @UE21H2HHD

👍 1

proxy-super also isn't thread safe, it works by mutating the proxy obiect

Yogesvara Das15:08:44

Is there a way to add a custom error message to spec if a s/def fails?

Drew Verlee15:08:58

I'm not sure about doing this through spec directly, but i think expound allows for this. Expound is what i use for custom human readable errors for spec.

☝️ 1
Drew Verlee15:08:22

malli can probably do this to as it's more a batteries included.

Alex Miller (Clojure team)15:08:20

No, not really. You can provide a custom explain function overall by binding clojure.spec.alpha/explain-out but you're kind of taking over the whole explain printing job then


Is there some Clojurians meta channel I'm not seeing, for discussing the state of this Slack workspace? Or should I just ask a question about that here? or just keep my thoughts myself? or....


#community-development probably.


always happy to hear thoughts.


thanks. see you over there.