Ian Cottrell 1aef897494 internal/lsp: fix for limitations of export data ... It is impossible to reconstruct a line and column correctly from export data, so we have to attempt to find open and process the file in order to guess what the original pos was when we have one that originated in export data. This occurs in any time in go to definition when the target is not in the same pacakge as the source. Change-Id: Ib2ee404d4f1c39d8bd7f1fbc2096d8d6cbeed6f8 Reviewed-on: https://go-review.googlesource.com/c/150044 Reviewed-by: Rebecca Stambler <rstambler@golang.org>		2018-11-19 18:00:18 +00:00
..
basic.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
client.go	internal/jsonrpc2: change to a more synchronous dispatch model	2018-11-14 19:09:51 +00:00
diagnostics.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
doc.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
general.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
language.go	internal/lsp: add implementation of completion to LSP	2018-11-06 21:04:51 +00:00
printers.go	internal/lsp: fix for limitations of export data	2018-11-19 18:00:18 +00:00
protocol.go	internal/jsonrpc2: change to a more synchronous dispatch model	2018-11-14 19:09:51 +00:00
registration.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
server.go	internal/jsonrpc2: change to a more synchronous dispatch model	2018-11-14 19:09:51 +00:00
text.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
window.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00
workspace.go	internal/lsp: the core lsp protocol	2018-09-25 15:17:08 +00:00