For example, let's say I have some Java object factory, which provides methods such as

public SomeClass createSomeClass() { return new SomeClass(); }

I'd like to write code such as

(let [object (doto (.createSomeClass factory)
                (.setFoo 1)        ;; <- I'd like completion here
                (.setBar 2))       ;; <- and here   
      quuz   (.getQuuz object)]  ;; <- but also here
  (.toString quuz))

at the moment it feels like I need to write

(let [^SomeClass object (doto ^SomeClass (.createSomeClass factory)
                           (.setFoo 1)
                           (.setBar 2))   
      quuz   (.getQuuz object)]
  (.toString quuz))

Also, it looks like the autocomplete does not suggest any inherited methods, e.g. if SomeClass extends SomeOtherClass.

As for the first question, is your only concern having to write type hints? There are many reasons to write them, I summarized them in https://github.com/jonase/eastwood#reflection

> Also, it looks like the autocomplete does not suggest any inherited methods, I'll check. That would sound like a Compliment issue (@U06PNK4HG)

sure, I naturally have (set! *warn-on-reflection* true) like any good boy. But in this case those type hints are not strictly needed

how is factory defined?

I don't have the code at hand at the moment, but something like (def ^ObjectFactory factory (ObjectFactory.)). The use case here is building a hierarchy tree of objects when doing XML generation from java classes.

Yep, that type hint looks like a correct (type-hinted) declaration. Generally, type tags propagate nicely across def s, let s, -> and so on. It's a non-trivial problem to solve but Compliment solves a good chunk of it. Feel free to verify that for a good variety of simple (and not-so-simple) expressions, we offer the right completion for a given interop object. If you can check that a) it works for certain cases and b) it doesn't work for a certain code shape (e.g. let + doto), it would be reasonable to create an issue in Compliment.

I assume Compliment is alexander-yakushev/compliment? Sure, I can document a couple of examples of my problem there

https://github.com/alexander-yakushev/compliment/issues/113

Log output is not supposed to be handled that way and would warrant a GH issue, will be happy to attend it swiftly

Oh, I just found cider-sync-tooling-eval. seems like something I can use.

In case you want to use cider-interactive-eval this should work :

(cider-interactive-eval "(+ 1 2)" nil nil `(("ns" "user")))

interactive-eval is async, I needed something simpler. I just wrote this: https://clojurians.slack.com/archives/C03S1KBA2/p1699647418659749?thread_ts=1699572048.111389&cid=C03S1KBA2