-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
goimports
functionality
#145
Comments
See #75. This tool does not aim to replace goimports. You can use both at the same time. This question and confusion keeps coming up, so I'll keep this issue open as a reminder to add a FAQ entry. |
That's unfortunate. Using both is more complicated and slower than using one. I use |
Remember that using goimports as a tool will always be slow. It has to load a lot of information from disk and/or the network, especially to guess what package/module is missing. So, if you want to be efficient with fixing imports, the answer is an LSP. Fixing imports is separate from formatting. If you don't want to use an LSP because performance isn't your top priority, then running goimports and gofumpt as separate tools will not add significant overhead. |
Currently using
goimports
. Would prefergofumpt
for stricter fmting, but the lack of automatic import editing is a show-stopper. Any chance this could be integrated?The text was updated successfully, but these errors were encountered: