You’re welcome! I’m glad it’s useful to you.
Sort of, Cursive does type inference in the editor for Java interop right now, so with enough information you can get useful information:
Now Cursive knows the types of things:
And these types can be used when completing. Here I’ve put the receiver first so that Cursive knows what I want to call interop on, and the completions only come from its type:
When I actually select a completion, Cursive will swap them around:
Even if you don’t swap things around for interop calls, the types are still useful. See here:
Here next() from Iterator is proposed as a completion, even if Iterator is not imported. This is because Cursive knows the local variables that are in scope, and will also add completions from their types even if they don’t appear in the code anywhere.
It’s possible, but I haven’t added it yet - I’ll get to it at some point.
