Robert Estelle

Thank you for your feedback! > > * Make module import lists explicit > > Maybe, but I think we should have a discussion about this with the other developers....

> Removing something completely also means that pointers to remembrance get lost. If documentation or commentary needs to refer to previous implementations, comments with commit IDs might better serve that...

@UlfNorell @andreasabel — Regarding `-fwarn-unused-binds` + `-fwarn-unused-imports` Those two flags are important for identifying dead dependencies and areas for pruning, and are useful to include to prevent regression. (I have...

> Out of curiosity, did removing unused imports get rid of a lot of dependencies? It got rid of a few, but #3527 doesn't really aim to do that yet:...

@jespercockx > > Installation process assumes that you have already installed and configured stack build tool. Currently importify works only with projects built with stack. > > We use cabal...

One note about this that I recently came across: beyond build + rebuild times, and regardless of improvements to the actual inter-module coupling, the "everything open-exports and open-imports" style is...

@nad — That's fine, I just wanted to create an issue to attach to discussion/information about the idea. @banacorn You've definitely done more in this area than anyone else. I...

I agree those wouldn't be covered by the server part of the LSP, though don't see why they'd need to. Clients like `agda-mode` could continue to implement additional functionalities like...

I've rebased this to cover the gpgsig changes along with a couple tiny related cleanups in that area.

This branch has been good to go for a few months but I've pushed up a rebase to fix a `mypy` checking issue introduced by a conflict with the recently...