Refactor nrepl has a locals op

Using tools.analyzer. 🙂

The problem with it is that overall complexity of the code rose a lot by adding it, not to mention some features there require parsing all project files which is pretty slow. That’s why I was wary of relying on it in CIDER itself. If it’s usage is limited to locals that’d be fine, though.

(and there’s also the fact that to generate the AST you have to evaluate the code, which not everyone is expecting) 🙂

interesting thought: - apropos - test - ns ops - more? all have ns & var filtering designed in a custom ad-hoc way. It would be really useful to extend apropos to support search-ns being a filtered list based on whether it's a project ns or not, for example.

I wonder if it should be a DSL supporting and/or? Probably too complicated right?

yeah, no client would ever send that

Something quite short works surprisingly well

It's a good opportunity to have ns-vars return vars from multiple namespaces too, e.g. {:op "ns-vars", :ns-query {:filter-regexps [#"clojure\.core"]} Get all clojure core namespaces {:op "ns-vars", :ns-query {:exactly 'clojure.core}} Only clojure core {:op "ns-vars", :ns-query {:project? true}} Only vars in the current project {:op "ns-vars", :ns-query {}} All vars

Adding metadata support as requested for tests becomes more generally useful too!

> all have ns & var filtering designed in a custom ad-hoc way. It would be really useful to extend apropos to support search-ns being a filtered list based on whether it’s a project ns or not, for example.

That’s a very good point! Unfortunately the API evolved naturally (chaotically) and we didn’t give much thought to making it uniform. Actually I’ve been thinking about this for a while now both for orchard and cider-nrepl and I think it’s really important to work in this direction. The work’s not much (or complex), but would make the API usage way easier and consistent.

Same goes for refactor-nrepl - many things there are wildly different from cider-nrepl and there’s no reason for this difference most of the time.

cider is organic growth, so is orchard 😛. I suppose there's rarely much motivation to do a sweeping "fix" like this.

If I make this change, I'm likely to cause downstream pain for you.

I could make it in a backwards compatible way, now that I think about it, only using ns-query if none of the "deprecated" attributes are there.

I’m not very worried about this - updating the client usages doesn’t take much time. I’m willing to deal with that effort in the name of better future for everyone. 🙂

Yeah, if you’re willing to make it work in backward compatible manner that’d be best, although ideally we should also send some deprecation warnings to the clients, so they authors would update them.

I’m not fond of the approach of keeping around compatibility code forever.

Heresy! Accretion is the future.

Oh wow, I could totally kill test-ns, as it's just a way of doing (ns/list-vars {:ns-query {:exactly #{'clojure.core-test}} :test? true})

@benedek these changes would also work very nicely with your new op for listing tests

Yep, that seems reasonable to me.

There's one little hack in here for special symbols, but otherwise this is looking to be a fairly clean abstraction.

I'm trying to figure out: A) Whether apropos has much value beyond sorting B) Whether to match the regex behaviour, or to extend it to allow a regex for both doc & name.

hey, i'm debugging an issue with emacs + saving files being slow, and i think cider is to blame -- as soon as i have established some connections, emacs file saving starts using 100% CPU for about 15 seconds

i did elp-instrument-package on cider, and it looks like cider-resolve-var has an elapsed time of 13s

i have 3 repl sessions as we speak

anyone has an idea what might cause this ?

i'm running 0.17snapshot, according to cider-version

it seems like this started getting worse quite recently

@lmergen Seems that’s caused by dynamic indentation. You can just disable it.

aha!

does it have to do with agressive-indent-mode ?

It’s strange that so many people started reported issues with dynamic font-locking and dynamic indentation lately - we haven’t really changed them in years.

> does it have to do with agressive-indent-mode ?

The interaction between the two is very painful as the dynamic indent is not as fast as the static one.

I’d never use agressive-indent-mode with cider’s dynamic indent.

let me test without agressive indent

That’s one more reminder that we need to cache this info to avoid the excessive calls to cider-resolve-var.

100% this is the issue

i disabled the mode and everything's fine

(basically you can’t know the indentation for something before you “resolve” it - know what it truly is, and that’s not super fast)

i see

Btw, I’ll likely cut the new CIDER release on Monday. If anyone wants to get some last minute fixes in - the weekend is the time to do so. That applies to me as well. 😄

https://github.com/clojure-emacs/orchard/blob/0e4fde5536c4afe6efd89922213909a442d88a9c/src/orchard/apropos.clj#L48 this looks like something that can be done on the/by the client.

is that reasonable? or should I retain this behaviour?

I'm thinking of, at the least, pushing it to the nrepl layer

the filtering should be taking regexes directly.

Yeah, definitely. Some things in orchard look odd just because they simply retained semantics of their middleware usage.

I guess you’re referring to the format, right? No idea why this is done on the Clojure side. Maybe to make the clients have to work less.

yeah, the formatting looks way off to me.

That was the only thing I could think of, but it seems like it masks complexity, it stops you from using any of the other flags.

Yeah, I agree.

Likely I didn’t even notice this when the code was originally written.

I've got a nice set of tests setup for the var/ns filtering, looks great. Passes the apropos tests too, might go back to those and decide about call signatures, but otherwise looking good.

Oh, there's an apropos test which tests the namespace list, which is gone now. I'll re-implement some of those in terms that make more sense as a whole.

okay, now the tests are really passing 🙂 I commented out the ordering rules and didn't notice.

I'm expecting to do a pull request on orchard tomorrow morning, and then start finishing my changes to cider tomorrow, hopefully a pull request in the afternoon.