commit | c16d0be617945651bc69957c71a95eab34e4994c | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Thu Jul 27 12:35:06 2023 -0400 |
committer | Gopher Robot <gobot@golang.org> | Mon Jul 31 12:54:47 2023 +0000 |
tree | 01e3d169cfc781ec64581ec3e3c098e28f630e6f | |
parent | 304e203aec2f01b5d279aeb91e4b191524f99ae5 [diff] |
cmd/gonew: add new tool for starting a module by copying one This is an experimental command that perhaps would become "go new" once we have more experience with it. We want to enable people to experiment with it and write their own templates and see how it works, and for that we need to put it in a place where it's reasonable to ask users to fetch it from. That place is golang.org/x/tools/cmd/gonew. There is an earlier copy in rsc.io/tmp/gonew, but that isn't the right place for end users to be fetching something to try. Once the tool is checked in I intend to start a GitHub discussion asking for feedback and suggestions about what is missing. I hope we will be able to identify core functionality that handles a large fraction of use cases. I've been using the earlier version myself for a while, and I've found it very convenient even in other contexts, like I want the code for a given module and don't want to go look up its Git repo and so on: go new rsc.io/quote@v1.5.2 cd quote Change-Id: Ifc27cbd5d87ded89bc707b087b3f08fa70b1ef07 Reviewed-on: https://go-review.googlesource.com/c/tools/+/513737 gopls-CI: kokoro <noreply+kokoro@google.com> Run-TryBot: Russ Cox <rsc@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
This repository provides the golang.org/x/tools
module, comprising various tools and packages mostly for static analysis of Go programs, some of which are listed below. Use the “Go reference” link above for more information about any package.
It also contains the golang.org/x/tools/gopls
module, whose root package is a language-server protocol (LSP) server for Go. An LSP server analyses the source code of a project and responds to requests from a wide range of editors such as VSCode and Vim, allowing them to support IDE-like functionality.
Selected commands:
cmd/goimports
formats a Go program like go fmt
and additionally inserts import statements for any packages required by the file after it is edited.cmd/callgraph
prints the call graph of a Go program.cmd/digraph
is a utility for manipulating directed graphs in textual notation.cmd/stringer
generates declarations (including a String
method) for “enum” types.cmd/toolstash
is a utility to simplify working with multiple versions of the Go toolchain.These commands may be fetched with a command such as
go install golang.org/x/tools/cmd/goimports@latest
Selected packages:
go/ssa
provides a static single-assignment form (SSA) intermediate representation (IR) for Go programs, similar to a typical compiler, for use by analysis tools.
go/packages
provides a simple interface for loading, parsing, and type checking a complete Go program from source code.
go/analysis
provides a framework for modular static analysis of Go programs.
go/callgraph
provides call graphs of Go programs using a variety of algorithms with different trade-offs.
go/ast/inspector
provides an optimized means of traversing a Go parse tree for use in analysis tools.
go/cfg
provides a simple control-flow graph (CFG) for a Go function.
go/expect
reads Go source files used as test inputs and interprets special comments within them as queries or assertions for testing.
go/gcexportdata
and go/gccgoexportdata
read and write the binary files containing type information used by the standard and gccgo
compilers.
go/types/objectpath
provides a stable naming scheme for named entities (“objects”) in the go/types
API.
Numerous other packages provide more esoteric functionality.
This repository uses Gerrit for code changes. To learn how to submit changes, 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.
This repository uses prettier to format JS and CSS files.
The version of prettier
used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.