Open denpeshkov opened 10 months ago
Thanks for the report; I can reproduce and confirm this bug using gopls@master. Possibly a dup or relative of #58461.
FWIW, improving refactoring (including renaming) will be a major focus of our team this year.
Go version
devel go1.22-1d45a7ef56 darwin/arm64
Output of
go env
in your module/workspace:What did you do?
==> ./foo/foo.go <==
==> ./bar/bar.go <==
==> ./qux/qux.go <==
The renaming of the function
foo/I.F()
tofoo/I.FF()
doesn't propagate tobar/S.F()
Checked with both
gopls@v0.15.0-pre.1
in VSCode andgorename
What did you see happen?
bar/S.F()
renamed tobar/S.FF()
What did you expect to see?
bar/s.F()
is not renamed