| commit | 77e3bb0ad9e72123a382fe9c4870b269210dab83 | [log] [tgz] |
|---|---|---|
| author | Dmitri Shuralyov <dmitshur@golang.org> | Mon Sep 23 11:03:52 2019 -0400 |
| committer | Dmitri Shuralyov <dmitshur@golang.org> | Wed Nov 13 19:18:52 2019 +0000 |
| tree | d69e3811b761f51e5de42a7548f7611f7ca99a3d | |
| parent | b2a5ed324b9110f8c455697c32fc1ea4bad924f9 [diff] |
go/packages/packagestest: add package use example The purpose and value of packagestest is easy to understand. However, the current API may not be easy to get started with. It includes identifiers such as Exporter, Exported, Export, whose names may not make it very clear in what order they are to be used, and whether the Exporter interfaces needs to be implemented by the caller. There are fairly common patterns of usage spread out across various packages that use packagestest. Add an example of basic usage to the documentation of this package that connects all of the pieces together, so that users don't have to look for it elsewhere. I would've preferred to add the example as example code¹, but it doesn't seem viable to write example code for test helper packages. There isn't a way to get a functional *testing.T in a func Example. ¹ https://golang.org/pkg/testing/#hdr-Examples Updates golang/go#33655 Change-Id: I0b15ff7974be25a71dfd4b68f470441ce7331d18 Reviewed-on: https://go-review.googlesource.com/c/tools/+/196980 Reviewed-by: Michael Matloob <matloob@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.