As long as the compiler knows that these are primitives coming in/out, that should work

But it may depend on the exact scenario

I can verify it doesn't Given

(defn primf [^long x ^long y] (fn [^long z] ,,,))
(reduce (fn [f' f] (fn [^long x] (or (f x) (f' x)))) (map (fn [[x y]] (primf x y)) pairs-of-longs))

higher order functions are always boxed

loop/recur (or macros that produce one like areduce etc) are really the only way to stay with primitives for something like this

Well, not the only way, but I cheated hard

After all, functions are just objects, and who am I to deny their nature? :thinking_face:

I have a thing that may be relevant https://gist.github.com/hiredman/d6ea3e30be757fef6da6

That's similar to what I ended up doing

There already exists "Rich Already Answered That!". Maybe there should be "Kevin Already Made a Gist on That!". :D

There's a thesis for a reflective tower of interpreters as a compiler for clojure just waiting to be written

I've seen (defmulti ^{:doc "some doc} foo ...) but not an example with defmethod

I could do the same, of course it doesn't show up when calling (doc foo) :thinking_face:

hint ) look at arglists of defmulti

:arglists '([name docstring? attr-map? dispatch-fn & options])

so you can add docstring placing a string right after the name

@U04V4KLKC yes but that's for defmulti, not defmethod

my bad, sorry )

so you are looking for a way to add a "comment" to defmethod? asking because docstring make sence only attached to var

and for multimethod the var is the one declared via defmulti. defmethod is for mutating it.

Yes, since defmethod doesn't make a new var, there's nothing to attach the docstring to. But you can make that var yourself and attach the docstring to that:

(defmulti f identity)

(defn f-x
  "f-x does f on x"
  [x]
  ...)

(defmethod f :x [x] (f-x x))

thanks 🙂 that clarifies my thought process

@U2FRKM4TW you can achieve the same via (defmethod f :x "f-x does f on x" [x] ...) scratch that ) I was wrong

maybe with (defmethod ^{:doc "f x does f on x"} f :x [arg] ...)

You cannot. There are no vars involved with defmethod.

It is actually a feature 🙂 After all, when calling a multi-method, you should regard it as just a method and don’t depend on implementation details such as the individual method implementations.

not really what you're asking but related: (apply require clojure.main/repl-requires) (notice nothing is quoted) - this will put all the usual stuff that you get in the initial ns (pprint, doc, source, javadoc, etc.) into the current ns

not really built-in, but you can customize your repl any way you like doing something like https://insideclojure.org/2020/02/11/custom-repl/

interesting, running a require before evaluating every repl input

That looks like just what I need @U064X3EF3, but I’ve been trying to put it into my deps file under :aliases :dev without success (using cider), seems like perhaps cider’s connection overwrites the :main-opts (?)

hard for me to guess how it might interact with cider or what those aliases do

The aliases just add :extra-paths and cider’s connection string looks like this:

/opt/homebrew/bin/clojure -Sdeps '{:deps {nrepl/nrepl {:mvn/version "0.9.0"} cider/cider-nrepl {:mvn/version "0.28.3"} refactor-nrepl/refactor-nrepl {:mvn/version "3.4.1"}} :aliases {:cider/nrepl {:main-opts ["-m" "nrepl.cmdline" "--middleware" "[refactor-nrepl.middleware/wrap-refactor,cider.nrepl/cider-middleware]"]}}}' -Mdev:test:cider/nrepl

main opts cannot concatenate. CIDER needs nrepl’s main to start the nrepl server. But nrepl doesn’t play nice with subrepls clojure.main repls anyways so it won’t work after solving the main opts problem

highlighting: :aliases {:cider/nrepl {:main-opts ["-m" "nrepl.cmdline" "--middleware" "[refactor-nrepl.middleware/wrap-refactor,cider.nrepl/cider-middleware]"]

not sure if it is directly related to this but each evaluation in nrepl calls clojure.main/repl for the form sent: https://github.com/nrepl/nrepl/blob/master/src/clojure/nrepl/middleware/interruptible_eval.clj#L84

I see @U11BV7MTK. Is there a way to solve the main problem in cider, i.e. autoloading a certain ns everywhere?

i like things like a namespace called on an added classpath root

then require once and then use fqn

what is fqn?

fully qualified name

personally, I find this kind of stuff to be too much magic for me to remember - if I want something, I just require it

Your probably right. Thanks for the responses.

for a while I had a dev function in my user ns, so I could call (user/dev) to do all the requires/ refers in the current ns, but nowadays I just require as needed (including frequent usage of (apply require clojure.main/repl-requires) )

i have the apply require clojure.main/repl-requires bound to C-c h and it evaluates that snippet. makes each namespace an IDE 🙂

Great ideas, thanks!

that’s not an option for me, unfortunately…must AOT

AOT in ci?