godef: incorrect results when package identifier does not match import path
Opened this issue · 1 comments
GoogleCodeExporter commented
godef optimistically assumes that it can deduce the package
identifier from the import path. This is often, but not
always the case. It should actually import the package
in question, although this will slow things down a little bit.
Original issue reported on code.google.com by rogpeppe@gmail.com
on 31 Jul 2014 at 8:08
GoogleCodeExporter commented
any update?
Original comment by ying.zhe...@gmail.com
on 20 Feb 2015 at 8:08