Also check out GitHub - hrzndhrn/recode: A linter with autocorrection and a refactoring tool. for other goodies.

That was my thinking. I had forgotten about recode as I haven’t tried it yet. A few months ago I was getting deep into syntax rewriting for a package I was working on, but then I got a new job (or rather a job, period) and haven’t been back to it yet.

Naw, I’ve just been feeling that my “hot take” to “attempted helpful solution” ratio has been off lately—it’s my own neurosis Really I default to not aliasing at all, except that there are non-insignificant number of situations where I do so it’s not a very useful thing to say in a forum reply. And of course it’s a personal taste kinda deal.

I feel for something like this to be bullet-proof you’d want to use Sourceror to figure out what is unsed aliases and remove them (this would work for those who use {}).

This will likely come off as a “nobody asked you” type of statement but my solution to this is to call alias close to where they are used, ie, the same logic that is applied to setting variables. If a group of functions use the same alias I put it above the first one and it acts like a “section divider”. If only one function uses an alias I call alias right in the function itself. I find it helps a lot with readability—if I jump to a function in a module I’m unfamiliar with, I don’t have to them jump to the top figure out if it has dependencies. I also never feel the annoyance of forgetting to delete aliases because it’s usually within view. I did, however, feel your pain when I worked on a codebase where everything had to be aliased and always be at the top.

I’m not trying to preach or anything. To each their own, of course!

do i understand corrently that you’re suggesting to analyze and edit AST so the rules i set are more precise and less fuzzy?

looks like recode (suggested by @dimitarvp) takes this approach (without fixing this particular problem).

not at all, in fact i asked how people solve this now. so exactly what i wanted. sounds like perhaps you’ve gotten pushback for this suggestion before?

interesting approach. i’ll think about this for my own processes. seems a bit messy in the end, but then again could actually reduce noise in a lot of situations i imagine.

hey nice! cool find. thanks. it’s interesting that it doesn’t do unused removal.

another tool i was suggested in private is elixir-styler - seems like they used Sourceror also, but dropped it due to speed. what do you think of this package, should I PR this one or recode? (if i ever get to that)