some deletions

[dotfiles/.git] / .config / coc / extensions / coc-go-data / tools / pkg / mod / golang.org / x / tools@v0.0.0-20201028153306-37f0764111ff / internal / lsp / helper / README.md

diff --git a/.config/coc/extensions/coc-go-data/tools/pkg/mod/golang.org/x/tools@v0.0.0-20201028153306-37f0764111ff/internal/lsp/helper/README.md b/.config/coc/extensions/coc-go-data/tools/pkg/mod/golang.org/x/tools@v0.0.0-20201028153306-37f0764111ff/internal/lsp/helper/README.md
deleted file mode 100644 (file)
index 3c51efe..0000000
--- a/.config/coc/extensions/coc-go-data/tools/pkg/mod/golang.org/x/tools@v0.0.0-20201028153306-37f0764111ff/internal/lsp/helper/README.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Generate server_gen.go
-
-`helper` generates boilerplate code for server.go by processing the
-generated code in `protocol/tsserver.go`.
-
-First, build `helper` in this directory (`go build .`).
-
-In directory `lsp`, executing `go generate server.go` generates the stylized file
-`server_gen.go` that contains stubs for type `Server`.
-
-It decides what stubs are needed and their signatures
-by looking at the `Server` interface (`-t` flag). These all look somewhat like
-`Resolve(context.Context, *CompletionItem) (*CompletionItem, error)`.
-
-It then parses the `lsp` directory (`-u` flag) to see if there is a corresponding
-implementation function (which in this case would be named `resolve`). If so
-it discovers the parameter names needed, and generates (in `server_gen.go`) code
-like
-
-``` go
-func (s *Server) resolve(ctx context.Context, params *protocol.CompletionItem) (*protocol.CompletionItem, error) {
-    return s.resolve(ctx, params)
-}
-```
-
-If `resolve` is not defined (and it is not), then the body of the generated function is
-
-```go
-    return nil, notImplemented("resolve")
-```
-
-So to add a capability currently not implemented, just define it somewhere in `lsp`.
-In this case, just define `func (s *Server) resolve(...)` and re-generate `server_gen.go`.