Karthik Nayak 377464f22d internal/lsp: include function literals in outgoing call hierarchy ... Currently we don't consider function literals in outgoing call hierarchy, because we only consider expressions of type `ast.SelectorExpr` and `ast.Ident`. So function literals are skipped. Fix this by ensuring we traverse through other types even if we don't add the type itself as an outgoing call hierarchy. Fixes golang/go#43438 Signed-off-by: Karthik Nayak <karthik.188@gmail.com> Change-Id: I9eacbd5ec7a68224518bf0e405319adeb673c853 GitHub-Last-Rev: 3e7118a8fd090b339a3eacf32fa8d62e05a76b87 GitHub-Pull-Request: golang/tools#320 Reviewed-on: https://go-review.googlesource.com/c/tools/+/323809 Reviewed-by: Rebecca Stambler <rstambler@golang.org> Trust: Rebecca Stambler <rstambler@golang.org> Trust: Peter Weinberger <pjw@google.com>		2021-06-01 22:58:04 +00:00
..
incoming	internal/lsp: remove multi-module support in tests	2020-09-22 16:28:30 +00:00
outgoing	internal/lsp: remove multi-module support in tests	2020-09-22 16:28:30 +00:00
callhierarchy.go	internal/lsp: include function literals in outgoing call hierarchy	2021-06-01 22:58:04 +00:00