-
Notifications
You must be signed in to change notification settings - Fork 17.4k
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
x/tools/internal/refactor/inline: analyzer generates unnecessary import renames #67281
Comments
cc: @adonovan |
Any update on this? |
I have a sketch of a fix but it was a little ugly and I haven't found time to improve it. Perhaps this week? I could also share it with @timothy-king since he's been keen to get his hands dirty in this package. |
I'm happy to take a stab at it myself if you don't have the capacity just wanted to make sure we are not duplicating work here. |
Change https://go.dev/cl/592575 mentions this issue: |
Change https://go.dev/cl/593035 mentions this issue: |
Go version
not relevant
Output of
go env
in your module/workspace:What did you do?
What did you see happen?
What did you expect to see?
I would expect the analyzer to not rename the import if it removes the conflicting import the same suggested fix.
This pattern is common when you use the inline analyzer to facilitate package moves and it would be nice if the analyzer doesn't leave the code base with a bunch of unecessary import renames.
The text was updated successfully, but these errors were encountered: