commit | 20ab64c0d93f083c2eb6362b7f17c7e094783a84 | [log] [tgz] |
---|---|---|
author | Peter Weinberger <pjw@google.com> | Mon Mar 09 12:51:18 2020 -0400 |
committer | Peter Weinberger <pjw@google.com> | Mon Mar 09 20:21:50 2020 +0000 |
tree | 5bb5a326ac89f0f1abfb00d340e0bd7f3b32e062 | |
parent | 92d517f97b4490f84787b6e354f43d426309669a [diff] |
internal/lsp: bring generated protocol code up to date; stop corrupting logs 1. logging at debug/rpc.go:105 was corrupting logs. 2. DocumentSymbol (a Server method) now returns []interface{}. 3. The latest version of the LSP changed CompletionItem.TextEdit to possibly be of the new type InsertReplaceEdit, so the generated Go code now has TextEdit an interface{} rather than a *TextEdit. This required a change to tests/util.go. 4. The latest version also introduced several other new types, and new members in some structs. Tests pass and the I've use the new gopls a little. Change-Id: Ic44d46f0c923882c9076c2754c1c85e09fbcaa2e Reviewed-on: https://go-review.googlesource.com/c/tools/+/222668 Run-TryBot: Peter Weinberger <pjw@google.com> Reviewed-by: Rebecca Stambler <rstambler@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools, godoc
and vet
for example, are included in binary Go distributions.
Others, including the Go guru
and the test coverage tool, can be fetched with go get
.
Packages include a type-checker for Go and an implementation of the Static Single Assignment form (SSA) representation for Go programs.
The easiest way to install is to run go get -u golang.org/x/tools/...
. You can also manually git clone the repository to $GOPATH/src/golang.org/x/tools
.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the tools repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/tools/(your subdir):” in the subject line, so it is easy to find.