Source file src/cmd/go/alldocs.go
1 // Copyright 2011 The Go Authors. All rights reserved. 2 // Use of this source code is governed by a BSD-style 3 // license that can be found in the LICENSE file. 4 5 // Code generated by 'go test cmd/go -v -run=^TestDocsUpToDate$ -fixdocs'; DO NOT EDIT. 6 // Edit the documentation in other files and then execute 'go generate cmd/go' to generate this one. 7 8 // Go is a tool for managing Go source code. 9 // 10 // Usage: 11 // 12 // go <command> [arguments] 13 // 14 // The commands are: 15 // 16 // bug start a bug report 17 // build compile packages and dependencies 18 // clean remove object files and cached files 19 // doc show documentation for package or symbol 20 // env print Go environment information 21 // fix update packages to use new APIs 22 // fmt gofmt (reformat) package sources 23 // generate generate Go files by processing source 24 // get add dependencies to current module and install them 25 // install compile and install packages and dependencies 26 // list list packages or modules 27 // mod module maintenance 28 // work workspace maintenance 29 // run compile and run Go program 30 // telemetry manage telemetry data and settings 31 // test test packages 32 // tool run specified go tool 33 // version print Go version 34 // vet report likely mistakes in packages 35 // 36 // Use "go help <command>" for more information about a command. 37 // 38 // Additional help topics: 39 // 40 // buildconstraint build constraints 41 // buildjson build -json encoding 42 // buildmode build modes 43 // c calling between Go and C 44 // cache build and test caching 45 // environment environment variables 46 // filetype file types 47 // goauth GOAUTH environment variable 48 // go.mod the go.mod file 49 // gopath GOPATH environment variable 50 // goproxy module proxy protocol 51 // importpath import path syntax 52 // modules modules, module versions, and more 53 // module-auth module authentication using go.sum 54 // packages package lists and patterns 55 // private configuration for downloading non-public code 56 // testflag testing flags 57 // testfunc testing functions 58 // vcs controlling version control with GOVCS 59 // 60 // Use "go help <topic>" for more information about that topic. 61 // 62 // # Start a bug report 63 // 64 // Usage: 65 // 66 // go bug 67 // 68 // Bug opens the default browser and starts a new bug report. 69 // The report includes useful system information. 70 // 71 // # Compile packages and dependencies 72 // 73 // Usage: 74 // 75 // go build [-o output] [build flags] [packages] 76 // 77 // Build compiles the packages named by the import paths, 78 // along with their dependencies, but it does not install the results. 79 // 80 // If the arguments to build are a list of .go files from a single directory, 81 // build treats them as a list of source files specifying a single package. 82 // 83 // When compiling packages, build ignores files that end in '_test.go'. 84 // 85 // When compiling a single main package, build writes the resulting 86 // executable to an output file named after the last non-major-version 87 // component of the package import path. The '.exe' suffix is added 88 // when writing a Windows executable. 89 // So 'go build example/sam' writes 'sam' or 'sam.exe'. 90 // 'go build example.com/foo/v2' writes 'foo' or 'foo.exe', not 'v2.exe'. 91 // 92 // When compiling a package from a list of .go files, the executable 93 // is named after the first source file. 94 // 'go build ed.go rx.go' writes 'ed' or 'ed.exe'. 95 // 96 // When compiling multiple packages or a single non-main package, 97 // build compiles the packages but discards the resulting object, 98 // serving only as a check that the packages can be built. 99 // 100 // The -o flag forces build to write the resulting executable or object 101 // to the named output file or directory, instead of the default behavior described 102 // in the last two paragraphs. If the named output is an existing directory or 103 // ends with a slash or backslash, then any resulting executables 104 // will be written to that directory. 105 // 106 // The build flags are shared by the build, clean, get, install, list, run, 107 // and test commands: 108 // 109 // -C dir 110 // Change to dir before running the command. 111 // Any files named on the command line are interpreted after 112 // changing directories. 113 // If used, this flag must be the first one in the command line. 114 // -a 115 // force rebuilding of packages that are already up-to-date. 116 // -n 117 // print the commands but do not run them. 118 // -p n 119 // the number of programs, such as build commands or 120 // test binaries, that can be run in parallel. 121 // The default is GOMAXPROCS, normally the number of CPUs available. 122 // -race 123 // enable data race detection. 124 // Supported only on linux/amd64, freebsd/amd64, darwin/amd64, darwin/arm64, windows/amd64, 125 // linux/ppc64le and linux/arm64 (only for 48-bit VMA). 126 // -msan 127 // enable interoperation with memory sanitizer. 128 // Supported only on linux/amd64, linux/arm64, linux/loong64, freebsd/amd64 129 // and only with Clang/LLVM as the host C compiler. 130 // PIE build mode will be used on all platforms except linux/amd64. 131 // -asan 132 // enable interoperation with address sanitizer. 133 // Supported only on linux/arm64, linux/amd64, linux/loong64. 134 // Supported on linux/amd64 or linux/arm64 and only with GCC 7 and higher 135 // or Clang/LLVM 9 and higher. 136 // And supported on linux/loong64 only with Clang/LLVM 16 and higher. 137 // -cover 138 // enable code coverage instrumentation. 139 // -covermode set,count,atomic 140 // set the mode for coverage analysis. 141 // The default is "set" unless -race is enabled, 142 // in which case it is "atomic". 143 // The values: 144 // set: bool: does this statement run? 145 // count: int: how many times does this statement run? 146 // atomic: int: count, but correct in multithreaded tests; 147 // significantly more expensive. 148 // Sets -cover. 149 // -coverpkg pattern1,pattern2,pattern3 150 // For a build that targets package 'main' (e.g. building a Go 151 // executable), apply coverage analysis to each package whose 152 // import path matches the patterns. The default is to apply 153 // coverage analysis to packages in the main Go module. See 154 // 'go help packages' for a description of package patterns. 155 // Sets -cover. 156 // -v 157 // print the names of packages as they are compiled. 158 // -work 159 // print the name of the temporary work directory and 160 // do not delete it when exiting. 161 // -x 162 // print the commands. 163 // -asmflags '[pattern=]arg list' 164 // arguments to pass on each go tool asm invocation. 165 // -buildmode mode 166 // build mode to use. See 'go help buildmode' for more. 167 // -buildvcs 168 // Whether to stamp binaries with version control information 169 // ("true", "false", or "auto"). By default ("auto"), version control 170 // information is stamped into a binary if the main package, the main module 171 // containing it, and the current directory are all in the same repository. 172 // Use -buildvcs=false to always omit version control information, or 173 // -buildvcs=true to error out if version control information is available but 174 // cannot be included due to a missing tool or ambiguous directory structure. 175 // -compiler name 176 // name of compiler to use, as in runtime.Compiler (gccgo or gc). 177 // -gccgoflags '[pattern=]arg list' 178 // arguments to pass on each gccgo compiler/linker invocation. 179 // -gcflags '[pattern=]arg list' 180 // arguments to pass on each go tool compile invocation. 181 // -installsuffix suffix 182 // a suffix to use in the name of the package installation directory, 183 // in order to keep output separate from default builds. 184 // If using the -race flag, the install suffix is automatically set to race 185 // or, if set explicitly, has _race appended to it. Likewise for the -msan 186 // and -asan flags. Using a -buildmode option that requires non-default compile 187 // flags has a similar effect. 188 // -json 189 // Emit build output in JSON suitable for automated processing. 190 // See 'go help buildjson' for the encoding details. 191 // -ldflags '[pattern=]arg list' 192 // arguments to pass on each go tool link invocation. 193 // -linkshared 194 // build code that will be linked against shared libraries previously 195 // created with -buildmode=shared. 196 // -mod mode 197 // module download mode to use: readonly, vendor, or mod. 198 // By default, if a vendor directory is present and the go version in go.mod 199 // is 1.14 or higher, the go command acts as if -mod=vendor were set. 200 // Otherwise, the go command acts as if -mod=readonly were set. 201 // See https://golang.org/ref/mod#build-commands for details. 202 // -modcacherw 203 // leave newly-created directories in the module cache read-write 204 // instead of making them read-only. 205 // -modfile file 206 // in module aware mode, read (and possibly write) an alternate go.mod 207 // file instead of the one in the module root directory. A file named 208 // "go.mod" must still be present in order to determine the module root 209 // directory, but it is not accessed. When -modfile is specified, an 210 // alternate go.sum file is also used: its path is derived from the 211 // -modfile flag by trimming the ".mod" extension and appending ".sum". 212 // -overlay file 213 // read a JSON config file that provides an overlay for build operations. 214 // The file is a JSON struct with a single field, named 'Replace', that 215 // maps each disk file path (a string) to its backing file path, so that 216 // a build will run as if the disk file path exists with the contents 217 // given by the backing file paths, or as if the disk file path does not 218 // exist if its backing file path is empty. Support for the -overlay flag 219 // has some limitations: importantly, cgo files included from outside the 220 // include path must be in the same directory as the Go package they are 221 // included from, and overlays will not appear when binaries and tests are 222 // run through go run and go test respectively. 223 // -pgo file 224 // specify the file path of a profile for profile-guided optimization (PGO). 225 // When the special name "auto" is specified, for each main package in the 226 // build, the go command selects a file named "default.pgo" in the package's 227 // directory if that file exists, and applies it to the (transitive) 228 // dependencies of the main package (other packages are not affected). 229 // Special name "off" turns off PGO. The default is "auto". 230 // -pkgdir dir 231 // install and load all packages from dir instead of the usual locations. 232 // For example, when building with a non-standard configuration, 233 // use -pkgdir to keep generated packages in a separate location. 234 // -tags tag,list 235 // a comma-separated list of additional build tags to consider satisfied 236 // during the build. For more information about build tags, see 237 // 'go help buildconstraint'. (Earlier versions of Go used a 238 // space-separated list, and that form is deprecated but still recognized.) 239 // -trimpath 240 // remove all file system paths from the resulting executable. 241 // Instead of absolute file system paths, the recorded file names 242 // will begin either a module path@version (when using modules), 243 // or a plain import path (when using the standard library, or GOPATH). 244 // -toolexec 'cmd args' 245 // a program to use to invoke toolchain programs like vet and asm. 246 // For example, instead of running asm, the go command will run 247 // 'cmd args /path/to/asm <arguments for asm>'. 248 // The TOOLEXEC_IMPORTPATH environment variable will be set, 249 // matching 'go list -f {{.ImportPath}}' for the package being built. 250 // 251 // The -asmflags, -gccgoflags, -gcflags, and -ldflags flags accept a 252 // space-separated list of arguments to pass to an underlying tool 253 // during the build. To embed spaces in an element in the list, surround 254 // it with either single or double quotes. The argument list may be 255 // preceded by a package pattern and an equal sign, which restricts 256 // the use of that argument list to the building of packages matching 257 // that pattern (see 'go help packages' for a description of package 258 // patterns). Without a pattern, the argument list applies only to the 259 // packages named on the command line. The flags may be repeated 260 // with different patterns in order to specify different arguments for 261 // different sets of packages. If a package matches patterns given in 262 // multiple flags, the latest match on the command line wins. 263 // For example, 'go build -gcflags=-S fmt' prints the disassembly 264 // only for package fmt, while 'go build -gcflags=all=-S fmt' 265 // prints the disassembly for fmt and all its dependencies. 266 // 267 // For more about specifying packages, see 'go help packages'. 268 // For more about where packages and binaries are installed, 269 // run 'go help gopath'. 270 // For more about calling between Go and C/C++, run 'go help c'. 271 // 272 // Note: Build adheres to certain conventions such as those described 273 // by 'go help gopath'. Not all projects can follow these conventions, 274 // however. Installations that have their own conventions or that use 275 // a separate software build system may choose to use lower-level 276 // invocations such as 'go tool compile' and 'go tool link' to avoid 277 // some of the overheads and design decisions of the build tool. 278 // 279 // See also: go install, go get, go clean. 280 // 281 // # Remove object files and cached files 282 // 283 // Usage: 284 // 285 // go clean [-i] [-r] [-cache] [-testcache] [-modcache] [-fuzzcache] [build flags] [packages] 286 // 287 // Clean removes object files from package source directories. 288 // The go command builds most objects in a temporary directory, 289 // so go clean is mainly concerned with object files left by other 290 // tools or by manual invocations of go build. 291 // 292 // If a package argument is given or the -i or -r flag is set, 293 // clean removes the following files from each of the 294 // source directories corresponding to the import paths: 295 // 296 // _obj/ old object directory, left from Makefiles 297 // _test/ old test directory, left from Makefiles 298 // _testmain.go old gotest file, left from Makefiles 299 // test.out old test log, left from Makefiles 300 // build.out old test log, left from Makefiles 301 // *.[568ao] object files, left from Makefiles 302 // 303 // DIR(.exe) from go build 304 // DIR.test(.exe) from go test -c 305 // MAINFILE(.exe) from go build MAINFILE.go 306 // *.so from SWIG 307 // 308 // In the list, DIR represents the final path element of the 309 // directory, and MAINFILE is the base name of any Go source 310 // file in the directory that is not included when building 311 // the package. 312 // 313 // The -i flag causes clean to remove the corresponding installed 314 // archive or binary (what 'go install' would create). 315 // 316 // The -n flag causes clean to print the remove commands it would execute, 317 // but not run them. 318 // 319 // The -r flag causes clean to be applied recursively to all the 320 // dependencies of the packages named by the import paths. 321 // 322 // The -x flag causes clean to print remove commands as it executes them. 323 // 324 // The -cache flag causes clean to remove the entire go build cache. 325 // 326 // The -testcache flag causes clean to expire all test results in the 327 // go build cache. 328 // 329 // The -modcache flag causes clean to remove the entire module 330 // download cache, including unpacked source code of versioned 331 // dependencies. 332 // 333 // The -fuzzcache flag causes clean to remove files stored in the Go build 334 // cache for fuzz testing. The fuzzing engine caches files that expand 335 // code coverage, so removing them may make fuzzing less effective until 336 // new inputs are found that provide the same coverage. These files are 337 // distinct from those stored in testdata directory; clean does not remove 338 // those files. 339 // 340 // For more about build flags, see 'go help build'. 341 // 342 // For more about specifying packages, see 'go help packages'. 343 // 344 // # Show documentation for package or symbol 345 // 346 // Usage: 347 // 348 // go doc [doc flags] [package|[package.]symbol[.methodOrField]] 349 // 350 // Doc prints the documentation comments associated with the item identified by its 351 // arguments (a package, const, func, type, var, method, or struct field) 352 // followed by a one-line summary of each of the first-level items "under" 353 // that item (package-level declarations for a package, methods for a type, 354 // etc.). 355 // 356 // Doc accepts zero, one, or two arguments. 357 // 358 // Given no arguments, that is, when run as 359 // 360 // go doc 361 // 362 // it prints the package documentation for the package in the current directory. 363 // If the package is a command (package main), the exported symbols of the package 364 // are elided from the presentation unless the -cmd flag is provided. 365 // 366 // When run with one argument, the argument is treated as a Go-syntax-like 367 // representation of the item to be documented. What the argument selects depends 368 // on what is installed in GOROOT and GOPATH, as well as the form of the argument, 369 // which is schematically one of these: 370 // 371 // go doc <pkg> 372 // go doc <sym>[.<methodOrField>] 373 // go doc [<pkg>.]<sym>[.<methodOrField>] 374 // go doc [<pkg>.][<sym>.]<methodOrField> 375 // 376 // The first item in this list matched by the argument is the one whose documentation 377 // is printed. (See the examples below.) However, if the argument starts with a capital 378 // letter it is assumed to identify a symbol or method in the current directory. 379 // 380 // For packages, the order of scanning is determined lexically in breadth-first order. 381 // That is, the package presented is the one that matches the search and is nearest 382 // the root and lexically first at its level of the hierarchy. The GOROOT tree is 383 // always scanned in its entirety before GOPATH. 384 // 385 // If there is no package specified or matched, the package in the current 386 // directory is selected, so "go doc Foo" shows the documentation for symbol Foo in 387 // the current package. 388 // 389 // The package path must be either a qualified path or a proper suffix of a 390 // path. The go tool's usual package mechanism does not apply: package path 391 // elements like . and ... are not implemented by go doc. 392 // 393 // When run with two arguments, the first is a package path (full path or suffix), 394 // and the second is a symbol, or symbol with method or struct field: 395 // 396 // go doc <pkg> <sym>[.<methodOrField>] 397 // 398 // In all forms, when matching symbols, lower-case letters in the argument match 399 // either case but upper-case letters match exactly. This means that there may be 400 // multiple matches of a lower-case argument in a package if different symbols have 401 // different cases. If this occurs, documentation for all matches is printed. 402 // 403 // Examples: 404 // 405 // go doc 406 // Show documentation for current package. 407 // go doc Foo 408 // Show documentation for Foo in the current package. 409 // (Foo starts with a capital letter so it cannot match 410 // a package path.) 411 // go doc encoding/json 412 // Show documentation for the encoding/json package. 413 // go doc json 414 // Shorthand for encoding/json. 415 // go doc json.Number (or go doc json.number) 416 // Show documentation and method summary for json.Number. 417 // go doc json.Number.Int64 (or go doc json.number.int64) 418 // Show documentation for json.Number's Int64 method. 419 // go doc cmd/doc 420 // Show package docs for the doc command. 421 // go doc -cmd cmd/doc 422 // Show package docs and exported symbols within the doc command. 423 // go doc template.new 424 // Show documentation for html/template's New function. 425 // (html/template is lexically before text/template) 426 // go doc text/template.new # One argument 427 // Show documentation for text/template's New function. 428 // go doc text/template new # Two arguments 429 // Show documentation for text/template's New function. 430 // 431 // At least in the current tree, these invocations all print the 432 // documentation for json.Decoder's Decode method: 433 // 434 // go doc json.Decoder.Decode 435 // go doc json.decoder.decode 436 // go doc json.decode 437 // cd go/src/encoding/json; go doc decode 438 // 439 // Flags: 440 // 441 // -all 442 // Show all the documentation for the package. 443 // -c 444 // Respect case when matching symbols. 445 // -cmd 446 // Treat a command (package main) like a regular package. 447 // Otherwise package main's exported symbols are hidden 448 // when showing the package's top-level documentation. 449 // -short 450 // One-line representation for each symbol. 451 // -src 452 // Show the full source code for the symbol. This will 453 // display the full Go source of its declaration and 454 // definition, such as a function definition (including 455 // the body), type declaration or enclosing const 456 // block. The output may therefore include unexported 457 // details. 458 // -u 459 // Show documentation for unexported as well as exported 460 // symbols, methods, and fields. 461 // 462 // # Print Go environment information 463 // 464 // Usage: 465 // 466 // go env [-json] [-changed] [-u] [-w] [var ...] 467 // 468 // Env prints Go environment information. 469 // 470 // By default env prints information as a shell script 471 // (on Windows, a batch file). If one or more variable 472 // names is given as arguments, env prints the value of 473 // each named variable on its own line. 474 // 475 // The -json flag prints the environment in JSON format 476 // instead of as a shell script. 477 // 478 // The -u flag requires one or more arguments and unsets 479 // the default setting for the named environment variables, 480 // if one has been set with 'go env -w'. 481 // 482 // The -w flag requires one or more arguments of the 483 // form NAME=VALUE and changes the default settings 484 // of the named environment variables to the given values. 485 // 486 // The -changed flag prints only those settings whose effective 487 // value differs from the default value that would be obtained in 488 // an empty environment with no prior uses of the -w flag. 489 // 490 // For more about environment variables, see 'go help environment'. 491 // 492 // # Update packages to use new APIs 493 // 494 // Usage: 495 // 496 // go fix [-fix list] [packages] 497 // 498 // Fix runs the Go fix command on the packages named by the import paths. 499 // 500 // The -fix flag sets a comma-separated list of fixes to run. 501 // The default is all known fixes. 502 // (Its value is passed to 'go tool fix -r'.) 503 // 504 // For more about fix, see 'go doc cmd/fix'. 505 // For more about specifying packages, see 'go help packages'. 506 // 507 // To run fix with other options, run 'go tool fix'. 508 // 509 // See also: go fmt, go vet. 510 // 511 // # Gofmt (reformat) package sources 512 // 513 // Usage: 514 // 515 // go fmt [-n] [-x] [packages] 516 // 517 // Fmt runs the command 'gofmt -l -w' on the packages named 518 // by the import paths. It prints the names of the files that are modified. 519 // 520 // For more about gofmt, see 'go doc cmd/gofmt'. 521 // For more about specifying packages, see 'go help packages'. 522 // 523 // The -n flag prints commands that would be executed. 524 // The -x flag prints commands as they are executed. 525 // 526 // The -mod flag's value sets which module download mode 527 // to use: readonly or vendor. See 'go help modules' for more. 528 // 529 // To run gofmt with specific options, run gofmt itself. 530 // 531 // See also: go fix, go vet. 532 // 533 // # Generate Go files by processing source 534 // 535 // Usage: 536 // 537 // go generate [-run regexp] [-n] [-v] [-x] [build flags] [file.go... | packages] 538 // 539 // Generate runs commands described by directives within existing 540 // files. Those commands can run any process but the intent is to 541 // create or update Go source files. 542 // 543 // Go generate is never run automatically by go build, go test, 544 // and so on. It must be run explicitly. 545 // 546 // Go generate scans the file for directives, which are lines of 547 // the form, 548 // 549 // //go:generate command argument... 550 // 551 // (note: no leading spaces and no space in "//go") where command 552 // is the generator to be run, corresponding to an executable file 553 // that can be run locally. It must either be in the shell path 554 // (gofmt), a fully qualified path (/usr/you/bin/mytool), or a 555 // command alias, described below. 556 // 557 // Note that go generate does not parse the file, so lines that look 558 // like directives in comments or multiline strings will be treated 559 // as directives. 560 // 561 // The arguments to the directive are space-separated tokens or 562 // double-quoted strings passed to the generator as individual 563 // arguments when it is run. 564 // 565 // Quoted strings use Go syntax and are evaluated before execution; a 566 // quoted string appears as a single argument to the generator. 567 // 568 // To convey to humans and machine tools that code is generated, 569 // generated source should have a line that matches the following 570 // regular expression (in Go syntax): 571 // 572 // ^// Code generated .* DO NOT EDIT\.$ 573 // 574 // This line must appear before the first non-comment, non-blank 575 // text in the file. 576 // 577 // Go generate sets several variables when it runs the generator: 578 // 579 // $GOARCH 580 // The execution architecture (arm, amd64, etc.) 581 // $GOOS 582 // The execution operating system (linux, windows, etc.) 583 // $GOFILE 584 // The base name of the file. 585 // $GOLINE 586 // The line number of the directive in the source file. 587 // $GOPACKAGE 588 // The name of the package of the file containing the directive. 589 // $GOROOT 590 // The GOROOT directory for the 'go' command that invoked the 591 // generator, containing the Go toolchain and standard library. 592 // $DOLLAR 593 // A dollar sign. 594 // $PATH 595 // The $PATH of the parent process, with $GOROOT/bin 596 // placed at the beginning. This causes generators 597 // that execute 'go' commands to use the same 'go' 598 // as the parent 'go generate' command. 599 // 600 // Other than variable substitution and quoted-string evaluation, no 601 // special processing such as "globbing" is performed on the command 602 // line. 603 // 604 // As a last step before running the command, any invocations of any 605 // environment variables with alphanumeric names, such as $GOFILE or 606 // $HOME, are expanded throughout the command line. The syntax for 607 // variable expansion is $NAME on all operating systems. Due to the 608 // order of evaluation, variables are expanded even inside quoted 609 // strings. If the variable NAME is not set, $NAME expands to the 610 // empty string. 611 // 612 // A directive of the form, 613 // 614 // //go:generate -command xxx args... 615 // 616 // specifies, for the remainder of this source file only, that the 617 // string xxx represents the command identified by the arguments. This 618 // can be used to create aliases or to handle multiword generators. 619 // For example, 620 // 621 // //go:generate -command foo go tool foo 622 // 623 // specifies that the command "foo" represents the generator 624 // "go tool foo". 625 // 626 // Generate processes packages in the order given on the command line, 627 // one at a time. If the command line lists .go files from a single directory, 628 // they are treated as a single package. Within a package, generate processes the 629 // source files in a package in file name order, one at a time. Within 630 // a source file, generate runs generators in the order they appear 631 // in the file, one at a time. The go generate tool also sets the build 632 // tag "generate" so that files may be examined by go generate but ignored 633 // during build. 634 // 635 // For packages with invalid code, generate processes only source files with a 636 // valid package clause. 637 // 638 // If any generator returns an error exit status, "go generate" skips 639 // all further processing for that package. 640 // 641 // The generator is run in the package's source directory. 642 // 643 // Go generate accepts two specific flags: 644 // 645 // -run="" 646 // if non-empty, specifies a regular expression to select 647 // directives whose full original source text (excluding 648 // any trailing spaces and final newline) matches the 649 // expression. 650 // 651 // -skip="" 652 // if non-empty, specifies a regular expression to suppress 653 // directives whose full original source text (excluding 654 // any trailing spaces and final newline) matches the 655 // expression. If a directive matches both the -run and 656 // the -skip arguments, it is skipped. 657 // 658 // It also accepts the standard build flags including -v, -n, and -x. 659 // The -v flag prints the names of packages and files as they are 660 // processed. 661 // The -n flag prints commands that would be executed. 662 // The -x flag prints commands as they are executed. 663 // 664 // For more about build flags, see 'go help build'. 665 // 666 // For more about specifying packages, see 'go help packages'. 667 // 668 // # Add dependencies to current module and install them 669 // 670 // Usage: 671 // 672 // go get [-t] [-u] [-tool] [build flags] [packages] 673 // 674 // Get resolves its command-line arguments to packages at specific module versions, 675 // updates go.mod to require those versions, and downloads source code into the 676 // module cache. 677 // 678 // To add a dependency for a package or upgrade it to its latest version: 679 // 680 // go get example.com/pkg 681 // 682 // To upgrade or downgrade a package to a specific version: 683 // 684 // go get example.com/pkg@v1.2.3 685 // 686 // To remove a dependency on a module and downgrade modules that require it: 687 // 688 // go get example.com/mod@none 689 // 690 // To upgrade the minimum required Go version to the latest released Go version: 691 // 692 // go get go@latest 693 // 694 // To upgrade the Go toolchain to the latest patch release of the current Go toolchain: 695 // 696 // go get toolchain@patch 697 // 698 // See https://golang.org/ref/mod#go-get for details. 699 // 700 // In earlier versions of Go, 'go get' was used to build and install packages. 701 // Now, 'go get' is dedicated to adjusting dependencies in go.mod. 'go install' 702 // may be used to build and install commands instead. When a version is specified, 703 // 'go install' runs in module-aware mode and ignores the go.mod file in the 704 // current directory. For example: 705 // 706 // go install example.com/pkg@v1.2.3 707 // go install example.com/pkg@latest 708 // 709 // See 'go help install' or https://golang.org/ref/mod#go-install for details. 710 // 711 // 'go get' accepts the following flags. 712 // 713 // The -t flag instructs get to consider modules needed to build tests of 714 // packages specified on the command line. 715 // 716 // The -u flag instructs get to update modules providing dependencies 717 // of packages named on the command line to use newer minor or patch 718 // releases when available. 719 // 720 // The -u=patch flag (not -u patch) also instructs get to update dependencies, 721 // but changes the default to select patch releases. 722 // 723 // When the -t and -u flags are used together, get will update 724 // test dependencies as well. 725 // 726 // The -tool flag instructs go to add a matching tool line to go.mod for each 727 // listed package. If -tool is used with @none, the line will be removed. 728 // 729 // The -x flag prints commands as they are executed. This is useful for 730 // debugging version control commands when a module is downloaded directly 731 // from a repository. 732 // 733 // For more about build flags, see 'go help build'. 734 // 735 // For more about modules, see https://golang.org/ref/mod. 736 // 737 // For more about using 'go get' to update the minimum Go version and 738 // suggested Go toolchain, see https://go.dev/doc/toolchain. 739 // 740 // For more about specifying packages, see 'go help packages'. 741 // 742 // See also: go build, go install, go clean, go mod. 743 // 744 // # Compile and install packages and dependencies 745 // 746 // Usage: 747 // 748 // go install [build flags] [packages] 749 // 750 // Install compiles and installs the packages named by the import paths. 751 // 752 // Executables are installed in the directory named by the GOBIN environment 753 // variable, which defaults to $GOPATH/bin or $HOME/go/bin if the GOPATH 754 // environment variable is not set. Executables in $GOROOT 755 // are installed in $GOROOT/bin or $GOTOOLDIR instead of $GOBIN. 756 // 757 // If the arguments have version suffixes (like @latest or @v1.0.0), "go install" 758 // builds packages in module-aware mode, ignoring the go.mod file in the current 759 // directory or any parent directory, if there is one. This is useful for 760 // installing executables without affecting the dependencies of the main module. 761 // To eliminate ambiguity about which module versions are used in the build, the 762 // arguments must satisfy the following constraints: 763 // 764 // - Arguments must be package paths or package patterns (with "..." wildcards). 765 // They must not be standard packages (like fmt), meta-patterns (std, cmd, 766 // all), or relative or absolute file paths. 767 // 768 // - All arguments must have the same version suffix. Different queries are not 769 // allowed, even if they refer to the same version. 770 // 771 // - All arguments must refer to packages in the same module at the same version. 772 // 773 // - Package path arguments must refer to main packages. Pattern arguments 774 // will only match main packages. 775 // 776 // - No module is considered the "main" module. If the module containing 777 // packages named on the command line has a go.mod file, it must not contain 778 // directives (replace and exclude) that would cause it to be interpreted 779 // differently than if it were the main module. The module must not require 780 // a higher version of itself. 781 // 782 // - Vendor directories are not used in any module. (Vendor directories are not 783 // included in the module zip files downloaded by 'go install'.) 784 // 785 // If the arguments don't have version suffixes, "go install" may run in 786 // module-aware mode or GOPATH mode, depending on the GO111MODULE environment 787 // variable and the presence of a go.mod file. See 'go help modules' for details. 788 // If module-aware mode is enabled, "go install" runs in the context of the main 789 // module. 790 // 791 // When module-aware mode is disabled, non-main packages are installed in the 792 // directory $GOPATH/pkg/$GOOS_$GOARCH. When module-aware mode is enabled, 793 // non-main packages are built and cached but not installed. 794 // 795 // Before Go 1.20, the standard library was installed to 796 // $GOROOT/pkg/$GOOS_$GOARCH. 797 // Starting in Go 1.20, the standard library is built and cached but not installed. 798 // Setting GODEBUG=installgoroot=all restores the use of 799 // $GOROOT/pkg/$GOOS_$GOARCH. 800 // 801 // For more about build flags, see 'go help build'. 802 // 803 // For more about specifying packages, see 'go help packages'. 804 // 805 // See also: go build, go get, go clean. 806 // 807 // # List packages or modules 808 // 809 // Usage: 810 // 811 // go list [-f format] [-json] [-m] [list flags] [build flags] [packages] 812 // 813 // List lists the named packages, one per line. 814 // The most commonly-used flags are -f and -json, which control the form 815 // of the output printed for each package. Other list flags, documented below, 816 // control more specific details. 817 // 818 // The default output shows the package import path: 819 // 820 // bytes 821 // encoding/json 822 // github.com/gorilla/mux 823 // golang.org/x/net/html 824 // 825 // The -f flag specifies an alternate format for the list, using the 826 // syntax of package template. The default output is equivalent 827 // to -f '{{.ImportPath}}'. The struct being passed to the template is: 828 // 829 // type Package struct { 830 // Dir string // directory containing package sources 831 // ImportPath string // import path of package in dir 832 // ImportComment string // path in import comment on package statement 833 // Name string // package name 834 // Doc string // package documentation string 835 // Target string // install path 836 // Shlib string // the shared library that contains this package (only set when -linkshared) 837 // Goroot bool // is this package in the Go root? 838 // Standard bool // is this package part of the standard Go library? 839 // Stale bool // would 'go install' do anything for this package? 840 // StaleReason string // explanation for Stale==true 841 // Root string // Go root or Go path dir containing this package 842 // ConflictDir string // this directory shadows Dir in $GOPATH 843 // BinaryOnly bool // binary-only package (no longer supported) 844 // ForTest string // package is only for use in named test 845 // Export string // file containing export data (when using -export) 846 // BuildID string // build ID of the compiled package (when using -export) 847 // Module *Module // info about package's containing module, if any (can be nil) 848 // Match []string // command-line patterns matching this package 849 // DepOnly bool // package is only a dependency, not explicitly listed 850 // DefaultGODEBUG string // default GODEBUG setting, for main packages 851 // 852 // // Source files 853 // GoFiles []string // .go source files (excluding CgoFiles, TestGoFiles, XTestGoFiles) 854 // CgoFiles []string // .go source files that import "C" 855 // CompiledGoFiles []string // .go files presented to compiler (when using -compiled) 856 // IgnoredGoFiles []string // .go source files ignored due to build constraints 857 // IgnoredOtherFiles []string // non-.go source files ignored due to build constraints 858 // CFiles []string // .c source files 859 // CXXFiles []string // .cc, .cxx and .cpp source files 860 // MFiles []string // .m source files 861 // HFiles []string // .h, .hh, .hpp and .hxx source files 862 // FFiles []string // .f, .F, .for and .f90 Fortran source files 863 // SFiles []string // .s source files 864 // SwigFiles []string // .swig files 865 // SwigCXXFiles []string // .swigcxx files 866 // SysoFiles []string // .syso object files to add to archive 867 // TestGoFiles []string // _test.go files in package 868 // XTestGoFiles []string // _test.go files outside package 869 // 870 // // Embedded files 871 // EmbedPatterns []string // //go:embed patterns 872 // EmbedFiles []string // files matched by EmbedPatterns 873 // TestEmbedPatterns []string // //go:embed patterns in TestGoFiles 874 // TestEmbedFiles []string // files matched by TestEmbedPatterns 875 // XTestEmbedPatterns []string // //go:embed patterns in XTestGoFiles 876 // XTestEmbedFiles []string // files matched by XTestEmbedPatterns 877 // 878 // // Cgo directives 879 // CgoCFLAGS []string // cgo: flags for C compiler 880 // CgoCPPFLAGS []string // cgo: flags for C preprocessor 881 // CgoCXXFLAGS []string // cgo: flags for C++ compiler 882 // CgoFFLAGS []string // cgo: flags for Fortran compiler 883 // CgoLDFLAGS []string // cgo: flags for linker 884 // CgoPkgConfig []string // cgo: pkg-config names 885 // 886 // // Dependency information 887 // Imports []string // import paths used by this package 888 // ImportMap map[string]string // map from source import to ImportPath (identity entries omitted) 889 // Deps []string // all (recursively) imported dependencies 890 // TestImports []string // imports from TestGoFiles 891 // XTestImports []string // imports from XTestGoFiles 892 // 893 // // Error information 894 // Incomplete bool // this package or a dependency has an error 895 // Error *PackageError // error loading package 896 // DepsErrors []*PackageError // errors loading dependencies 897 // } 898 // 899 // Packages stored in vendor directories report an ImportPath that includes the 900 // path to the vendor directory (for example, "d/vendor/p" instead of "p"), 901 // so that the ImportPath uniquely identifies a given copy of a package. 902 // The Imports, Deps, TestImports, and XTestImports lists also contain these 903 // expanded import paths. See golang.org/s/go15vendor for more about vendoring. 904 // 905 // The error information, if any, is 906 // 907 // type PackageError struct { 908 // ImportStack []string // shortest path from package named on command line to this one 909 // Pos string // position of error (if present, file:line:col) 910 // Err string // the error itself 911 // } 912 // 913 // The module information is a Module struct, defined in the discussion 914 // of list -m below. 915 // 916 // The template function "join" calls strings.Join. 917 // 918 // The template function "context" returns the build context, defined as: 919 // 920 // type Context struct { 921 // GOARCH string // target architecture 922 // GOOS string // target operating system 923 // GOROOT string // Go root 924 // GOPATH string // Go path 925 // CgoEnabled bool // whether cgo can be used 926 // UseAllFiles bool // use files regardless of //go:build lines, file names 927 // Compiler string // compiler to assume when computing target paths 928 // BuildTags []string // build constraints to match in //go:build lines 929 // ToolTags []string // toolchain-specific build constraints 930 // ReleaseTags []string // releases the current release is compatible with 931 // InstallSuffix string // suffix to use in the name of the install dir 932 // } 933 // 934 // For more information about the meaning of these fields see the documentation 935 // for the go/build package's Context type. 936 // 937 // The -json flag causes the package data to be printed in JSON format 938 // instead of using the template format. The JSON flag can optionally be 939 // provided with a set of comma-separated required field names to be output. 940 // If so, those required fields will always appear in JSON output, but 941 // others may be omitted to save work in computing the JSON struct. 942 // 943 // The -compiled flag causes list to set CompiledGoFiles to the Go source 944 // files presented to the compiler. Typically this means that it repeats 945 // the files listed in GoFiles and then also adds the Go code generated 946 // by processing CgoFiles and SwigFiles. The Imports list contains the 947 // union of all imports from both GoFiles and CompiledGoFiles. 948 // 949 // The -deps flag causes list to iterate over not just the named packages 950 // but also all their dependencies. It visits them in a depth-first post-order 951 // traversal, so that a package is listed only after all its dependencies. 952 // Packages not explicitly listed on the command line will have the DepOnly 953 // field set to true. 954 // 955 // The -e flag changes the handling of erroneous packages, those that 956 // cannot be found or are malformed. By default, the list command 957 // prints an error to standard error for each erroneous package and 958 // omits the packages from consideration during the usual printing. 959 // With the -e flag, the list command never prints errors to standard 960 // error and instead processes the erroneous packages with the usual 961 // printing. Erroneous packages will have a non-empty ImportPath and 962 // a non-nil Error field; other information may or may not be missing 963 // (zeroed). 964 // 965 // The -export flag causes list to set the Export field to the name of a 966 // file containing up-to-date export information for the given package, 967 // and the BuildID field to the build ID of the compiled package. 968 // 969 // The -find flag causes list to identify the named packages but not 970 // resolve their dependencies: the Imports and Deps lists will be empty. 971 // With the -find flag, the -deps, -test and -export commands cannot be 972 // used. 973 // 974 // The -test flag causes list to report not only the named packages 975 // but also their test binaries (for packages with tests), to convey to 976 // source code analysis tools exactly how test binaries are constructed. 977 // The reported import path for a test binary is the import path of 978 // the package followed by a ".test" suffix, as in "math/rand.test". 979 // When building a test, it is sometimes necessary to rebuild certain 980 // dependencies specially for that test (most commonly the tested 981 // package itself). The reported import path of a package recompiled 982 // for a particular test binary is followed by a space and the name of 983 // the test binary in brackets, as in "math/rand [math/rand.test]" 984 // or "regexp [sort.test]". The ForTest field is also set to the name 985 // of the package being tested ("math/rand" or "sort" in the previous 986 // examples). 987 // 988 // The Dir, Target, Shlib, Root, ConflictDir, and Export file paths 989 // are all absolute paths. 990 // 991 // By default, the lists GoFiles, CgoFiles, and so on hold names of files in Dir 992 // (that is, paths relative to Dir, not absolute paths). 993 // The generated files added when using the -compiled and -test flags 994 // are absolute paths referring to cached copies of generated Go source files. 995 // Although they are Go source files, the paths may not end in ".go". 996 // 997 // The -m flag causes list to list modules instead of packages. 998 // 999 // When listing modules, the -f flag still specifies a format template 1000 // applied to a Go struct, but now a Module struct: 1001 // 1002 // type Module struct { 1003 // Path string // module path 1004 // Query string // version query corresponding to this version 1005 // Version string // module version 1006 // Versions []string // available module versions 1007 // Replace *Module // replaced by this module 1008 // Time *time.Time // time version was created 1009 // Update *Module // available update (with -u) 1010 // Main bool // is this the main module? 1011 // Indirect bool // module is only indirectly needed by main module 1012 // Dir string // directory holding local copy of files, if any 1013 // GoMod string // path to go.mod file describing module, if any 1014 // GoVersion string // go version used in module 1015 // Retracted []string // retraction information, if any (with -retracted or -u) 1016 // Deprecated string // deprecation message, if any (with -u) 1017 // Error *ModuleError // error loading module 1018 // Sum string // checksum for path, version (as in go.sum) 1019 // GoModSum string // checksum for go.mod (as in go.sum) 1020 // Origin any // provenance of module 1021 // Reuse bool // reuse of old module info is safe 1022 // } 1023 // 1024 // type ModuleError struct { 1025 // Err string // the error itself 1026 // } 1027 // 1028 // The file GoMod refers to may be outside the module directory if the 1029 // module is in the module cache or if the -modfile flag is used. 1030 // 1031 // The default output is to print the module path and then 1032 // information about the version and replacement if any. 1033 // For example, 'go list -m all' might print: 1034 // 1035 // my/main/module 1036 // golang.org/x/text v0.3.0 => /tmp/text 1037 // rsc.io/pdf v0.1.1 1038 // 1039 // The Module struct has a String method that formats this 1040 // line of output, so that the default format is equivalent 1041 // to -f '{{.String}}'. 1042 // 1043 // Note that when a module has been replaced, its Replace field 1044 // describes the replacement module, and its Dir field is set to 1045 // the replacement's source code, if present. (That is, if Replace 1046 // is non-nil, then Dir is set to Replace.Dir, with no access to 1047 // the replaced source code.) 1048 // 1049 // The -u flag adds information about available upgrades. 1050 // When the latest version of a given module is newer than 1051 // the current one, list -u sets the Module's Update field 1052 // to information about the newer module. list -u will also set 1053 // the module's Retracted field if the current version is retracted. 1054 // The Module's String method indicates an available upgrade by 1055 // formatting the newer version in brackets after the current version. 1056 // If a version is retracted, the string "(retracted)" will follow it. 1057 // For example, 'go list -m -u all' might print: 1058 // 1059 // my/main/module 1060 // golang.org/x/text v0.3.0 [v0.4.0] => /tmp/text 1061 // rsc.io/pdf v0.1.1 (retracted) [v0.1.2] 1062 // 1063 // (For tools, 'go list -m -u -json all' may be more convenient to parse.) 1064 // 1065 // The -versions flag causes list to set the Module's Versions field 1066 // to a list of all known versions of that module, ordered according 1067 // to semantic versioning, earliest to latest. The flag also changes 1068 // the default output format to display the module path followed by the 1069 // space-separated version list. 1070 // 1071 // The -retracted flag causes list to report information about retracted 1072 // module versions. When -retracted is used with -f or -json, the Retracted 1073 // field will be set to a string explaining why the version was retracted. 1074 // The string is taken from comments on the retract directive in the 1075 // module's go.mod file. When -retracted is used with -versions, retracted 1076 // versions are listed together with unretracted versions. The -retracted 1077 // flag may be used with or without -m. 1078 // 1079 // The arguments to list -m are interpreted as a list of modules, not packages. 1080 // The main module is the module containing the current directory. 1081 // The active modules are the main module and its dependencies. 1082 // With no arguments, list -m shows the main module. 1083 // With arguments, list -m shows the modules specified by the arguments. 1084 // Any of the active modules can be specified by its module path. 1085 // The special pattern "all" specifies all the active modules, first the main 1086 // module and then dependencies sorted by module path. 1087 // A pattern containing "..." specifies the active modules whose 1088 // module paths match the pattern. 1089 // A query of the form path@version specifies the result of that query, 1090 // which is not limited to active modules. 1091 // See 'go help modules' for more about module queries. 1092 // 1093 // The template function "module" takes a single string argument 1094 // that must be a module path or query and returns the specified 1095 // module as a Module struct. If an error occurs, the result will 1096 // be a Module struct with a non-nil Error field. 1097 // 1098 // When using -m, the -reuse=old.json flag accepts the name of file containing 1099 // the JSON output of a previous 'go list -m -json' invocation with the 1100 // same set of modifier flags (such as -u, -retracted, and -versions). 1101 // The go command may use this file to determine that a module is unchanged 1102 // since the previous invocation and avoid redownloading information about it. 1103 // Modules that are not redownloaded will be marked in the new output by 1104 // setting the Reuse field to true. Normally the module cache provides this 1105 // kind of reuse automatically; the -reuse flag can be useful on systems that 1106 // do not preserve the module cache. 1107 // 1108 // For more about build flags, see 'go help build'. 1109 // 1110 // For more about specifying packages, see 'go help packages'. 1111 // 1112 // For more about modules, see https://golang.org/ref/mod. 1113 // 1114 // # Module maintenance 1115 // 1116 // Go mod provides access to operations on modules. 1117 // 1118 // Note that support for modules is built into all the go commands, 1119 // not just 'go mod'. For example, day-to-day adding, removing, upgrading, 1120 // and downgrading of dependencies should be done using 'go get'. 1121 // See 'go help modules' for an overview of module functionality. 1122 // 1123 // Usage: 1124 // 1125 // go mod <command> [arguments] 1126 // 1127 // The commands are: 1128 // 1129 // download download modules to local cache 1130 // edit edit go.mod from tools or scripts 1131 // graph print module requirement graph 1132 // init initialize new module in current directory 1133 // tidy add missing and remove unused modules 1134 // vendor make vendored copy of dependencies 1135 // verify verify dependencies have expected content 1136 // why explain why packages or modules are needed 1137 // 1138 // Use "go help mod <command>" for more information about a command. 1139 // 1140 // # Download modules to local cache 1141 // 1142 // Usage: 1143 // 1144 // go mod download [-x] [-json] [-reuse=old.json] [modules] 1145 // 1146 // Download downloads the named modules, which can be module patterns selecting 1147 // dependencies of the main module or module queries of the form path@version. 1148 // 1149 // With no arguments, download applies to the modules needed to build and test 1150 // the packages in the main module: the modules explicitly required by the main 1151 // module if it is at 'go 1.17' or higher, or all transitively-required modules 1152 // if at 'go 1.16' or lower. 1153 // 1154 // The go command will automatically download modules as needed during ordinary 1155 // execution. The "go mod download" command is useful mainly for pre-filling 1156 // the local cache or to compute the answers for a Go module proxy. 1157 // 1158 // By default, download writes nothing to standard output. It may print progress 1159 // messages and errors to standard error. 1160 // 1161 // The -json flag causes download to print a sequence of JSON objects 1162 // to standard output, describing each downloaded module (or failure), 1163 // corresponding to this Go struct: 1164 // 1165 // type Module struct { 1166 // Path string // module path 1167 // Query string // version query corresponding to this version 1168 // Version string // module version 1169 // Error string // error loading module 1170 // Info string // absolute path to cached .info file 1171 // GoMod string // absolute path to cached .mod file 1172 // Zip string // absolute path to cached .zip file 1173 // Dir string // absolute path to cached source root directory 1174 // Sum string // checksum for path, version (as in go.sum) 1175 // GoModSum string // checksum for go.mod (as in go.sum) 1176 // Origin any // provenance of module 1177 // Reuse bool // reuse of old module info is safe 1178 // } 1179 // 1180 // The -reuse flag accepts the name of file containing the JSON output of a 1181 // previous 'go mod download -json' invocation. The go command may use this 1182 // file to determine that a module is unchanged since the previous invocation 1183 // and avoid redownloading it. Modules that are not redownloaded will be marked 1184 // in the new output by setting the Reuse field to true. Normally the module 1185 // cache provides this kind of reuse automatically; the -reuse flag can be 1186 // useful on systems that do not preserve the module cache. 1187 // 1188 // The -x flag causes download to print the commands download executes. 1189 // 1190 // See https://golang.org/ref/mod#go-mod-download for more about 'go mod download'. 1191 // 1192 // See https://golang.org/ref/mod#version-queries for more about version queries. 1193 // 1194 // # Edit go.mod from tools or scripts 1195 // 1196 // Usage: 1197 // 1198 // go mod edit [editing flags] [-fmt|-print|-json] [go.mod] 1199 // 1200 // Edit provides a command-line interface for editing go.mod, 1201 // for use primarily by tools or scripts. It reads only go.mod; 1202 // it does not look up information about the modules involved. 1203 // By default, edit reads and writes the go.mod file of the main module, 1204 // but a different target file can be specified after the editing flags. 1205 // 1206 // The editing flags specify a sequence of editing operations. 1207 // 1208 // The -fmt flag reformats the go.mod file without making other changes. 1209 // This reformatting is also implied by any other modifications that use or 1210 // rewrite the go.mod file. The only time this flag is needed is if no other 1211 // flags are specified, as in 'go mod edit -fmt'. 1212 // 1213 // The -module flag changes the module's path (the go.mod file's module line). 1214 // 1215 // The -godebug=key=value flag adds a godebug key=value line, 1216 // replacing any existing godebug lines with the given key. 1217 // 1218 // The -dropgodebug=key flag drops any existing godebug lines 1219 // with the given key. 1220 // 1221 // The -require=path@version and -droprequire=path flags 1222 // add and drop a requirement on the given module path and version. 1223 // Note that -require overrides any existing requirements on path. 1224 // These flags are mainly for tools that understand the module graph. 1225 // Users should prefer 'go get path@version' or 'go get path@none', 1226 // which make other go.mod adjustments as needed to satisfy 1227 // constraints imposed by other modules. 1228 // 1229 // The -go=version flag sets the expected Go language version. 1230 // This flag is mainly for tools that understand Go version dependencies. 1231 // Users should prefer 'go get go@version'. 1232 // 1233 // The -toolchain=version flag sets the Go toolchain to use. 1234 // This flag is mainly for tools that understand Go version dependencies. 1235 // Users should prefer 'go get toolchain@version'. 1236 // 1237 // The -exclude=path@version and -dropexclude=path@version flags 1238 // add and drop an exclusion for the given module path and version. 1239 // Note that -exclude=path@version is a no-op if that exclusion already exists. 1240 // 1241 // The -replace=old[@v]=new[@v] flag adds a replacement of the given 1242 // module path and version pair. If the @v in old@v is omitted, a 1243 // replacement without a version on the left side is added, which applies 1244 // to all versions of the old module path. If the @v in new@v is omitted, 1245 // the new path should be a local module root directory, not a module 1246 // path. Note that -replace overrides any redundant replacements for old[@v], 1247 // so omitting @v will drop existing replacements for specific versions. 1248 // 1249 // The -dropreplace=old[@v] flag drops a replacement of the given 1250 // module path and version pair. If the @v is omitted, a replacement without 1251 // a version on the left side is dropped. 1252 // 1253 // The -retract=version and -dropretract=version flags add and drop a 1254 // retraction on the given version. The version may be a single version 1255 // like "v1.2.3" or a closed interval like "[v1.1.0,v1.1.9]". Note that 1256 // -retract=version is a no-op if that retraction already exists. 1257 // 1258 // The -tool=path and -droptool=path flags add and drop a tool declaration 1259 // for the given path. 1260 // 1261 // The -godebug, -dropgodebug, -require, -droprequire, -exclude, -dropexclude, 1262 // -replace, -dropreplace, -retract, -dropretract, -tool, and -droptool editing 1263 // flags may be repeated, and the changes are applied in the order given. 1264 // 1265 // The -print flag prints the final go.mod in its text format instead of 1266 // writing it back to go.mod. 1267 // 1268 // The -json flag prints the final go.mod file in JSON format instead of 1269 // writing it back to go.mod. The JSON output corresponds to these Go types: 1270 // 1271 // type Module struct { 1272 // Path string 1273 // Version string 1274 // } 1275 // 1276 // type GoMod struct { 1277 // Module ModPath 1278 // Go string 1279 // Toolchain string 1280 // Godebug []Godebug 1281 // Require []Require 1282 // Exclude []Module 1283 // Replace []Replace 1284 // Retract []Retract 1285 // } 1286 // 1287 // type ModPath struct { 1288 // Path string 1289 // Deprecated string 1290 // } 1291 // 1292 // type Godebug struct { 1293 // Key string 1294 // Value string 1295 // } 1296 // 1297 // type Require struct { 1298 // Path string 1299 // Version string 1300 // Indirect bool 1301 // } 1302 // 1303 // type Replace struct { 1304 // Old Module 1305 // New Module 1306 // } 1307 // 1308 // type Retract struct { 1309 // Low string 1310 // High string 1311 // Rationale string 1312 // } 1313 // 1314 // type Tool struct { 1315 // Path string 1316 // } 1317 // 1318 // Retract entries representing a single version (not an interval) will have 1319 // the "Low" and "High" fields set to the same value. 1320 // 1321 // Note that this only describes the go.mod file itself, not other modules 1322 // referred to indirectly. For the full set of modules available to a build, 1323 // use 'go list -m -json all'. 1324 // 1325 // Edit also provides the -C, -n, and -x build flags. 1326 // 1327 // See https://golang.org/ref/mod#go-mod-edit for more about 'go mod edit'. 1328 // 1329 // # Print module requirement graph 1330 // 1331 // Usage: 1332 // 1333 // go mod graph [-go=version] [-x] 1334 // 1335 // Graph prints the module requirement graph (with replacements applied) 1336 // in text form. Each line in the output has two space-separated fields: a module 1337 // and one of its requirements. Each module is identified as a string of the form 1338 // path@version, except for the main module, which has no @version suffix. 1339 // 1340 // The -go flag causes graph to report the module graph as loaded by the 1341 // given Go version, instead of the version indicated by the 'go' directive 1342 // in the go.mod file. 1343 // 1344 // The -x flag causes graph to print the commands graph executes. 1345 // 1346 // See https://golang.org/ref/mod#go-mod-graph for more about 'go mod graph'. 1347 // 1348 // # Initialize new module in current directory 1349 // 1350 // Usage: 1351 // 1352 // go mod init [module-path] 1353 // 1354 // Init initializes and writes a new go.mod file in the current directory, in 1355 // effect creating a new module rooted at the current directory. The go.mod file 1356 // must not already exist. 1357 // 1358 // Init accepts one optional argument, the module path for the new module. If the 1359 // module path argument is omitted, init will attempt to infer the module path 1360 // using import comments in .go files, vendoring tool configuration files (like 1361 // Gopkg.lock), and the current directory (if in GOPATH). 1362 // 1363 // See https://golang.org/ref/mod#go-mod-init for more about 'go mod init'. 1364 // 1365 // # Add missing and remove unused modules 1366 // 1367 // Usage: 1368 // 1369 // go mod tidy [-e] [-v] [-x] [-diff] [-go=version] [-compat=version] 1370 // 1371 // Tidy makes sure go.mod matches the source code in the module. 1372 // It adds any missing modules necessary to build the current module's 1373 // packages and dependencies, and it removes unused modules that 1374 // don't provide any relevant packages. It also adds any missing entries 1375 // to go.sum and removes any unnecessary ones. 1376 // 1377 // The -v flag causes tidy to print information about removed modules 1378 // to standard error. 1379 // 1380 // The -e flag causes tidy to attempt to proceed despite errors 1381 // encountered while loading packages. 1382 // 1383 // The -diff flag causes tidy not to modify go.mod or go.sum but 1384 // instead print the necessary changes as a unified diff. It exits 1385 // with a non-zero code if the diff is not empty. 1386 // 1387 // The -go flag causes tidy to update the 'go' directive in the go.mod 1388 // file to the given version, which may change which module dependencies 1389 // are retained as explicit requirements in the go.mod file. 1390 // (Go versions 1.17 and higher retain more requirements in order to 1391 // support lazy module loading.) 1392 // 1393 // The -compat flag preserves any additional checksums needed for the 1394 // 'go' command from the indicated major Go release to successfully load 1395 // the module graph, and causes tidy to error out if that version of the 1396 // 'go' command would load any imported package from a different module 1397 // version. By default, tidy acts as if the -compat flag were set to the 1398 // version prior to the one indicated by the 'go' directive in the go.mod 1399 // file. 1400 // 1401 // The -x flag causes tidy to print the commands download executes. 1402 // 1403 // See https://golang.org/ref/mod#go-mod-tidy for more about 'go mod tidy'. 1404 // 1405 // # Make vendored copy of dependencies 1406 // 1407 // Usage: 1408 // 1409 // go mod vendor [-e] [-v] [-o outdir] 1410 // 1411 // Vendor resets the main module's vendor directory to include all packages 1412 // needed to build and test all the main module's packages. 1413 // It does not include test code for vendored packages. 1414 // 1415 // The -v flag causes vendor to print the names of vendored 1416 // modules and packages to standard error. 1417 // 1418 // The -e flag causes vendor to attempt to proceed despite errors 1419 // encountered while loading packages. 1420 // 1421 // The -o flag causes vendor to create the vendor directory at the given 1422 // path instead of "vendor". The go command can only use a vendor directory 1423 // named "vendor" within the module root directory, so this flag is 1424 // primarily useful for other tools. 1425 // 1426 // See https://golang.org/ref/mod#go-mod-vendor for more about 'go mod vendor'. 1427 // 1428 // # Verify dependencies have expected content 1429 // 1430 // Usage: 1431 // 1432 // go mod verify 1433 // 1434 // Verify checks that the dependencies of the current module, 1435 // which are stored in a local downloaded source cache, have not been 1436 // modified since being downloaded. If all the modules are unmodified, 1437 // verify prints "all modules verified." Otherwise it reports which 1438 // modules have been changed and causes 'go mod' to exit with a 1439 // non-zero status. 1440 // 1441 // See https://golang.org/ref/mod#go-mod-verify for more about 'go mod verify'. 1442 // 1443 // # Explain why packages or modules are needed 1444 // 1445 // Usage: 1446 // 1447 // go mod why [-m] [-vendor] packages... 1448 // 1449 // Why shows a shortest path in the import graph from the main module to 1450 // each of the listed packages. If the -m flag is given, why treats the 1451 // arguments as a list of modules and finds a path to any package in each 1452 // of the modules. 1453 // 1454 // By default, why queries the graph of packages matched by "go list all", 1455 // which includes tests for reachable packages. The -vendor flag causes why 1456 // to exclude tests of dependencies. 1457 // 1458 // The output is a sequence of stanzas, one for each package or module 1459 // name on the command line, separated by blank lines. Each stanza begins 1460 // with a comment line "# package" or "# module" giving the target 1461 // package or module. Subsequent lines give a path through the import 1462 // graph, one package per line. If the package or module is not 1463 // referenced from the main module, the stanza will display a single 1464 // parenthesized note indicating that fact. 1465 // 1466 // For example: 1467 // 1468 // $ go mod why golang.org/x/text/language golang.org/x/text/encoding 1469 // # golang.org/x/text/language 1470 // rsc.io/quote 1471 // rsc.io/sampler 1472 // golang.org/x/text/language 1473 // 1474 // # golang.org/x/text/encoding 1475 // (main module does not need package golang.org/x/text/encoding) 1476 // $ 1477 // 1478 // See https://golang.org/ref/mod#go-mod-why for more about 'go mod why'. 1479 // 1480 // # Workspace maintenance 1481 // 1482 // Work provides access to operations on workspaces. 1483 // 1484 // Note that support for workspaces is built into many other commands, not 1485 // just 'go work'. 1486 // 1487 // See 'go help modules' for information about Go's module system of which 1488 // workspaces are a part. 1489 // 1490 // See https://go.dev/ref/mod#workspaces for an in-depth reference on 1491 // workspaces. 1492 // 1493 // See https://go.dev/doc/tutorial/workspaces for an introductory 1494 // tutorial on workspaces. 1495 // 1496 // A workspace is specified by a go.work file that specifies a set of 1497 // module directories with the "use" directive. These modules are used as 1498 // root modules by the go command for builds and related operations. A 1499 // workspace that does not specify modules to be used cannot be used to do 1500 // builds from local modules. 1501 // 1502 // go.work files are line-oriented. Each line holds a single directive, 1503 // made up of a keyword followed by arguments. For example: 1504 // 1505 // go 1.18 1506 // 1507 // use ../foo/bar 1508 // use ./baz 1509 // 1510 // replace example.com/foo v1.2.3 => example.com/bar v1.4.5 1511 // 1512 // The leading keyword can be factored out of adjacent lines to create a block, 1513 // like in Go imports. 1514 // 1515 // use ( 1516 // ../foo/bar 1517 // ./baz 1518 // ) 1519 // 1520 // The use directive specifies a module to be included in the workspace's 1521 // set of main modules. The argument to the use directive is the directory 1522 // containing the module's go.mod file. 1523 // 1524 // The go directive specifies the version of Go the file was written at. It 1525 // is possible there may be future changes in the semantics of workspaces 1526 // that could be controlled by this version, but for now the version 1527 // specified has no effect. 1528 // 1529 // The replace directive has the same syntax as the replace directive in a 1530 // go.mod file and takes precedence over replaces in go.mod files. It is 1531 // primarily intended to override conflicting replaces in different workspace 1532 // modules. 1533 // 1534 // To determine whether the go command is operating in workspace mode, use 1535 // the "go env GOWORK" command. This will specify the workspace file being 1536 // used. 1537 // 1538 // Usage: 1539 // 1540 // go work <command> [arguments] 1541 // 1542 // The commands are: 1543 // 1544 // edit edit go.work from tools or scripts 1545 // init initialize workspace file 1546 // sync sync workspace build list to modules 1547 // use add modules to workspace file 1548 // vendor make vendored copy of dependencies 1549 // 1550 // Use "go help work <command>" for more information about a command. 1551 // 1552 // # Edit go.work from tools or scripts 1553 // 1554 // Usage: 1555 // 1556 // go work edit [editing flags] [go.work] 1557 // 1558 // Edit provides a command-line interface for editing go.work, 1559 // for use primarily by tools or scripts. It only reads go.work; 1560 // it does not look up information about the modules involved. 1561 // If no file is specified, Edit looks for a go.work file in the current 1562 // directory and its parent directories 1563 // 1564 // The editing flags specify a sequence of editing operations. 1565 // 1566 // The -fmt flag reformats the go.work file without making other changes. 1567 // This reformatting is also implied by any other modifications that use or 1568 // rewrite the go.mod file. The only time this flag is needed is if no other 1569 // flags are specified, as in 'go work edit -fmt'. 1570 // 1571 // The -godebug=key=value flag adds a godebug key=value line, 1572 // replacing any existing godebug lines with the given key. 1573 // 1574 // The -dropgodebug=key flag drops any existing godebug lines 1575 // with the given key. 1576 // 1577 // The -use=path and -dropuse=path flags 1578 // add and drop a use directive from the go.work file's set of module directories. 1579 // 1580 // The -replace=old[@v]=new[@v] flag adds a replacement of the given 1581 // module path and version pair. If the @v in old@v is omitted, a 1582 // replacement without a version on the left side is added, which applies 1583 // to all versions of the old module path. If the @v in new@v is omitted, 1584 // the new path should be a local module root directory, not a module 1585 // path. Note that -replace overrides any redundant replacements for old[@v], 1586 // so omitting @v will drop existing replacements for specific versions. 1587 // 1588 // The -dropreplace=old[@v] flag drops a replacement of the given 1589 // module path and version pair. If the @v is omitted, a replacement without 1590 // a version on the left side is dropped. 1591 // 1592 // The -use, -dropuse, -replace, and -dropreplace, 1593 // editing flags may be repeated, and the changes are applied in the order given. 1594 // 1595 // The -go=version flag sets the expected Go language version. 1596 // 1597 // The -toolchain=name flag sets the Go toolchain to use. 1598 // 1599 // The -print flag prints the final go.work in its text format instead of 1600 // writing it back to go.mod. 1601 // 1602 // The -json flag prints the final go.work file in JSON format instead of 1603 // writing it back to go.mod. The JSON output corresponds to these Go types: 1604 // 1605 // type GoWork struct { 1606 // Go string 1607 // Toolchain string 1608 // Godebug []Godebug 1609 // Use []Use 1610 // Replace []Replace 1611 // } 1612 // 1613 // type Godebug struct { 1614 // Key string 1615 // Value string 1616 // } 1617 // 1618 // type Use struct { 1619 // DiskPath string 1620 // ModulePath string 1621 // } 1622 // 1623 // type Replace struct { 1624 // Old Module 1625 // New Module 1626 // } 1627 // 1628 // type Module struct { 1629 // Path string 1630 // Version string 1631 // } 1632 // 1633 // See the workspaces reference at https://go.dev/ref/mod#workspaces 1634 // for more information. 1635 // 1636 // # Initialize workspace file 1637 // 1638 // Usage: 1639 // 1640 // go work init [moddirs] 1641 // 1642 // Init initializes and writes a new go.work file in the 1643 // current directory, in effect creating a new workspace at the current 1644 // directory. 1645 // 1646 // go work init optionally accepts paths to the workspace modules as 1647 // arguments. If the argument is omitted, an empty workspace with no 1648 // modules will be created. 1649 // 1650 // Each argument path is added to a use directive in the go.work file. The 1651 // current go version will also be listed in the go.work file. 1652 // 1653 // See the workspaces reference at https://go.dev/ref/mod#workspaces 1654 // for more information. 1655 // 1656 // # Sync workspace build list to modules 1657 // 1658 // Usage: 1659 // 1660 // go work sync 1661 // 1662 // Sync syncs the workspace's build list back to the 1663 // workspace's modules 1664 // 1665 // The workspace's build list is the set of versions of all the 1666 // (transitive) dependency modules used to do builds in the workspace. go 1667 // work sync generates that build list using the Minimal Version Selection 1668 // algorithm, and then syncs those versions back to each of modules 1669 // specified in the workspace (with use directives). 1670 // 1671 // The syncing is done by sequentially upgrading each of the dependency 1672 // modules specified in a workspace module to the version in the build list 1673 // if the dependency module's version is not already the same as the build 1674 // list's version. Note that Minimal Version Selection guarantees that the 1675 // build list's version of each module is always the same or higher than 1676 // that in each workspace module. 1677 // 1678 // See the workspaces reference at https://go.dev/ref/mod#workspaces 1679 // for more information. 1680 // 1681 // # Add modules to workspace file 1682 // 1683 // Usage: 1684 // 1685 // go work use [-r] [moddirs] 1686 // 1687 // Use provides a command-line interface for adding 1688 // directories, optionally recursively, to a go.work file. 1689 // 1690 // A use directive will be added to the go.work file for each argument 1691 // directory listed on the command line go.work file, if it exists, 1692 // or removed from the go.work file if it does not exist. 1693 // Use fails if any remaining use directives refer to modules that 1694 // do not exist. 1695 // 1696 // Use updates the go line in go.work to specify a version at least as 1697 // new as all the go lines in the used modules, both preexisting ones 1698 // and newly added ones. With no arguments, this update is the only 1699 // thing that go work use does. 1700 // 1701 // The -r flag searches recursively for modules in the argument 1702 // directories, and the use command operates as if each of the directories 1703 // were specified as arguments. 1704 // 1705 // See the workspaces reference at https://go.dev/ref/mod#workspaces 1706 // for more information. 1707 // 1708 // # Make vendored copy of dependencies 1709 // 1710 // Usage: 1711 // 1712 // go work vendor [-e] [-v] [-o outdir] 1713 // 1714 // Vendor resets the workspace's vendor directory to include all packages 1715 // needed to build and test all the workspace's packages. 1716 // It does not include test code for vendored packages. 1717 // 1718 // The -v flag causes vendor to print the names of vendored 1719 // modules and packages to standard error. 1720 // 1721 // The -e flag causes vendor to attempt to proceed despite errors 1722 // encountered while loading packages. 1723 // 1724 // The -o flag causes vendor to create the vendor directory at the given 1725 // path instead of "vendor". The go command can only use a vendor directory 1726 // named "vendor" within the module root directory, so this flag is 1727 // primarily useful for other tools. 1728 // 1729 // # Compile and run Go program 1730 // 1731 // Usage: 1732 // 1733 // go run [build flags] [-exec xprog] package [arguments...] 1734 // 1735 // Run compiles and runs the named main Go package. 1736 // Typically the package is specified as a list of .go source files from a single 1737 // directory, but it may also be an import path, file system path, or pattern 1738 // matching a single known package, as in 'go run .' or 'go run my/cmd'. 1739 // 1740 // If the package argument has a version suffix (like @latest or @v1.0.0), 1741 // "go run" builds the program in module-aware mode, ignoring the go.mod file in 1742 // the current directory or any parent directory, if there is one. This is useful 1743 // for running programs without affecting the dependencies of the main module. 1744 // 1745 // If the package argument doesn't have a version suffix, "go run" may run in 1746 // module-aware mode or GOPATH mode, depending on the GO111MODULE environment 1747 // variable and the presence of a go.mod file. See 'go help modules' for details. 1748 // If module-aware mode is enabled, "go run" runs in the context of the main 1749 // module. 1750 // 1751 // By default, 'go run' runs the compiled binary directly: 'a.out arguments...'. 1752 // If the -exec flag is given, 'go run' invokes the binary using xprog: 1753 // 1754 // 'xprog a.out arguments...'. 1755 // 1756 // If the -exec flag is not given, GOOS or GOARCH is different from the system 1757 // default, and a program named go_$GOOS_$GOARCH_exec can be found 1758 // on the current search path, 'go run' invokes the binary using that program, 1759 // for example 'go_js_wasm_exec a.out arguments...'. This allows execution of 1760 // cross-compiled programs when a simulator or other execution method is 1761 // available. 1762 // 1763 // By default, 'go run' compiles the binary without generating the information 1764 // used by debuggers, to reduce build time. To include debugger information in 1765 // the binary, use 'go build'. 1766 // 1767 // The exit status of Run is not the exit status of the compiled binary. 1768 // 1769 // For more about build flags, see 'go help build'. 1770 // For more about specifying packages, see 'go help packages'. 1771 // 1772 // See also: go build. 1773 // 1774 // # Manage telemetry data and settings 1775 // 1776 // Usage: 1777 // 1778 // go telemetry [off|local|on] 1779 // 1780 // Telemetry is used to manage Go telemetry data and settings. 1781 // 1782 // Telemetry can be in one of three modes: off, local, or on. 1783 // 1784 // When telemetry is in local mode, counter data is written to the local file 1785 // system, but will not be uploaded to remote servers. 1786 // 1787 // When telemetry is off, local counter data is neither collected nor uploaded. 1788 // 1789 // When telemetry is on, telemetry data is written to the local file system 1790 // and periodically sent to https://telemetry.go.dev/. Uploaded data is used to 1791 // help improve the Go toolchain and related tools, and it will be published as 1792 // part of a public dataset. 1793 // 1794 // For more details, see https://telemetry.go.dev/privacy. 1795 // This data is collected in accordance with the Google Privacy Policy 1796 // (https://policies.google.com/privacy). 1797 // 1798 // To view the current telemetry mode, run "go telemetry". 1799 // To disable telemetry uploading, but keep local data collection, run 1800 // "go telemetry local". 1801 // To enable both collection and uploading, run “go telemetry on”. 1802 // To disable both collection and uploading, run "go telemetry off". 1803 // 1804 // The current telemetry mode is also available as the value of the 1805 // non-settable "GOTELEMETRY" go env variable. The directory in the 1806 // local file system that telemetry data is written to is available 1807 // as the value of the non-settable "GOTELEMETRYDIR" go env variable. 1808 // 1809 // See https://go.dev/doc/telemetry for more information on telemetry. 1810 // 1811 // # Test packages 1812 // 1813 // Usage: 1814 // 1815 // go test [build/test flags] [packages] [build/test flags & test binary flags] 1816 // 1817 // 'Go test' automates testing the packages named by the import paths. 1818 // It prints a summary of the test results in the format: 1819 // 1820 // ok archive/tar 0.011s 1821 // FAIL archive/zip 0.022s 1822 // ok compress/gzip 0.033s 1823 // ... 1824 // 1825 // followed by detailed output for each failed package. 1826 // 1827 // 'Go test' recompiles each package along with any files with names matching 1828 // the file pattern "*_test.go". 1829 // These additional files can contain test functions, benchmark functions, fuzz 1830 // tests and example functions. See 'go help testfunc' for more. 1831 // Each listed package causes the execution of a separate test binary. 1832 // Files whose names begin with "_" (including "_test.go") or "." are ignored. 1833 // 1834 // Test files that declare a package with the suffix "_test" will be compiled as a 1835 // separate package, and then linked and run with the main test binary. 1836 // 1837 // The go tool will ignore a directory named "testdata", making it available 1838 // to hold ancillary data needed by the tests. 1839 // 1840 // As part of building a test binary, go test runs go vet on the package 1841 // and its test source files to identify significant problems. If go vet 1842 // finds any problems, go test reports those and does not run the test 1843 // binary. Only a high-confidence subset of the default go vet checks are 1844 // used. That subset is: atomic, bool, buildtags, directive, errorsas, 1845 // ifaceassert, nilfunc, printf, stringintconv, and tests. You can see 1846 // the documentation for these and other vet tests via "go doc cmd/vet". 1847 // To disable the running of go vet, use the -vet=off flag. To run all 1848 // checks, use the -vet=all flag. 1849 // 1850 // All test output and summary lines are printed to the go command's 1851 // standard output, even if the test printed them to its own standard 1852 // error. (The go command's standard error is reserved for printing 1853 // errors building the tests.) 1854 // 1855 // The go command places $GOROOT/bin at the beginning of $PATH 1856 // in the test's environment, so that tests that execute 1857 // 'go' commands use the same 'go' as the parent 'go test' command. 1858 // 1859 // Go test runs in two different modes: 1860 // 1861 // The first, called local directory mode, occurs when go test is 1862 // invoked with no package arguments (for example, 'go test' or 'go 1863 // test -v'). In this mode, go test compiles the package sources and 1864 // tests found in the current directory and then runs the resulting 1865 // test binary. In this mode, caching (discussed below) is disabled. 1866 // After the package test finishes, go test prints a summary line 1867 // showing the test status ('ok' or 'FAIL'), package name, and elapsed 1868 // time. 1869 // 1870 // The second, called package list mode, occurs when go test is invoked 1871 // with explicit package arguments (for example 'go test math', 'go 1872 // test ./...', and even 'go test .'). In this mode, go test compiles 1873 // and tests each of the packages listed on the command line. If a 1874 // package test passes, go test prints only the final 'ok' summary 1875 // line. If a package test fails, go test prints the full test output. 1876 // If invoked with the -bench or -v flag, go test prints the full 1877 // output even for passing package tests, in order to display the 1878 // requested benchmark results or verbose logging. After the package 1879 // tests for all of the listed packages finish, and their output is 1880 // printed, go test prints a final 'FAIL' status if any package test 1881 // has failed. 1882 // 1883 // In package list mode only, go test caches successful package test 1884 // results to avoid unnecessary repeated running of tests. When the 1885 // result of a test can be recovered from the cache, go test will 1886 // redisplay the previous output instead of running the test binary 1887 // again. When this happens, go test prints '(cached)' in place of the 1888 // elapsed time in the summary line. 1889 // 1890 // The rule for a match in the cache is that the run involves the same 1891 // test binary and the flags on the command line come entirely from a 1892 // restricted set of 'cacheable' test flags, defined as -benchtime, -cpu, 1893 // -list, -parallel, -run, -short, -timeout, -failfast, -fullpath and -v. 1894 // If a run of go test has any test or non-test flags outside this set, 1895 // the result is not cached. To disable test caching, use any test flag 1896 // or argument other than the cacheable flags. The idiomatic way to disable 1897 // test caching explicitly is to use -count=1. Tests that open files within 1898 // the package's module or that consult environment variables only 1899 // match future runs in which the files and environment variables are 1900 // unchanged. A cached test result is treated as executing in no time 1901 // at all, so a successful package test result will be cached and 1902 // reused regardless of -timeout setting. 1903 // 1904 // In addition to the build flags, the flags handled by 'go test' itself are: 1905 // 1906 // -args 1907 // Pass the remainder of the command line (everything after -args) 1908 // to the test binary, uninterpreted and unchanged. 1909 // Because this flag consumes the remainder of the command line, 1910 // the package list (if present) must appear before this flag. 1911 // 1912 // -c 1913 // Compile the test binary to pkg.test in the current directory but do not run it 1914 // (where pkg is the last element of the package's import path). 1915 // The file name or target directory can be changed with the -o flag. 1916 // 1917 // -exec xprog 1918 // Run the test binary using xprog. The behavior is the same as 1919 // in 'go run'. See 'go help run' for details. 1920 // 1921 // -json 1922 // Convert test output to JSON suitable for automated processing. 1923 // See 'go doc test2json' for the encoding details. 1924 // Also emits build output in JSON. See 'go help buildjson'. 1925 // 1926 // -o file 1927 // Compile the test binary to the named file. 1928 // The test still runs (unless -c or -i is specified). 1929 // If file ends in a slash or names an existing directory, 1930 // the test is written to pkg.test in that directory. 1931 // 1932 // The test binary also accepts flags that control execution of the test; these 1933 // flags are also accessible by 'go test'. See 'go help testflag' for details. 1934 // 1935 // For more about build flags, see 'go help build'. 1936 // For more about specifying packages, see 'go help packages'. 1937 // 1938 // See also: go build, go vet. 1939 // 1940 // # Run specified go tool 1941 // 1942 // Usage: 1943 // 1944 // go tool [-n] command [args...] 1945 // 1946 // Tool runs the go tool command identified by the arguments. 1947 // 1948 // Go ships with a number of builtin tools, and additional tools 1949 // may be defined in the go.mod of the current module. 1950 // 1951 // With no arguments it prints the list of known tools. 1952 // 1953 // The -n flag causes tool to print the command that would be 1954 // executed but not execute it. 1955 // 1956 // For more about each builtin tool command, see 'go doc cmd/<command>'. 1957 // 1958 // # Print Go version 1959 // 1960 // Usage: 1961 // 1962 // go version [-m] [-v] [file ...] 1963 // 1964 // Version prints the build information for Go binary files. 1965 // 1966 // Go version reports the Go version used to build each of the named files. 1967 // 1968 // If no files are named on the command line, go version prints its own 1969 // version information. 1970 // 1971 // If a directory is named, go version walks that directory, recursively, 1972 // looking for recognized Go binaries and reporting their versions. 1973 // By default, go version does not report unrecognized files found 1974 // during a directory scan. The -v flag causes it to report unrecognized files. 1975 // 1976 // The -m flag causes go version to print each file's embedded 1977 // module version information, when available. In the output, the module 1978 // information consists of multiple lines following the version line, each 1979 // indented by a leading tab character. 1980 // 1981 // See also: go doc runtime/debug.BuildInfo. 1982 // 1983 // # Report likely mistakes in packages 1984 // 1985 // Usage: 1986 // 1987 // go vet [build flags] [-vettool prog] [vet flags] [packages] 1988 // 1989 // Vet runs the Go vet command on the packages named by the import paths. 1990 // 1991 // For more about vet and its flags, see 'go doc cmd/vet'. 1992 // For more about specifying packages, see 'go help packages'. 1993 // For a list of checkers and their flags, see 'go tool vet help'. 1994 // For details of a specific checker such as 'printf', see 'go tool vet help printf'. 1995 // 1996 // The -vettool=prog flag selects a different analysis tool with alternative 1997 // or additional checks. 1998 // For example, the 'shadow' analyzer can be built and run using these commands: 1999 // 2000 // go install golang.org/x/tools/go/analysis/passes/shadow/cmd/shadow@latest 2001 // go vet -vettool=$(which shadow) 2002 // 2003 // The build flags supported by go vet are those that control package resolution 2004 // and execution, such as -C, -n, -x, -v, -tags, and -toolexec. 2005 // For more about these flags, see 'go help build'. 2006 // 2007 // See also: go fmt, go fix. 2008 // 2009 // # Build constraints 2010 // 2011 // A build constraint, also known as a build tag, is a condition under which a 2012 // file should be included in the package. Build constraints are given by a 2013 // line comment that begins 2014 // 2015 // //go:build 2016 // 2017 // Build constraints can also be used to downgrade the language version 2018 // used to compile a file. 2019 // 2020 // Constraints may appear in any kind of source file (not just Go), but 2021 // they must appear near the top of the file, preceded 2022 // only by blank lines and other comments. These rules mean that in Go 2023 // files a build constraint must appear before the package clause. 2024 // 2025 // To distinguish build constraints from package documentation, 2026 // a build constraint should be followed by a blank line. 2027 // 2028 // A build constraint comment is evaluated as an expression containing 2029 // build tags combined by ||, &&, and ! operators and parentheses. 2030 // Operators have the same meaning as in Go. 2031 // 2032 // For example, the following build constraint constrains a file to 2033 // build when the "linux" and "386" constraints are satisfied, or when 2034 // "darwin" is satisfied and "cgo" is not: 2035 // 2036 // //go:build (linux && 386) || (darwin && !cgo) 2037 // 2038 // It is an error for a file to have more than one //go:build line. 2039 // 2040 // During a particular build, the following build tags are satisfied: 2041 // 2042 // - the target operating system, as spelled by runtime.GOOS, set with the 2043 // GOOS environment variable. 2044 // - the target architecture, as spelled by runtime.GOARCH, set with the 2045 // GOARCH environment variable. 2046 // - any architecture features, in the form GOARCH.feature 2047 // (for example, "amd64.v2"), as detailed below. 2048 // - "unix", if GOOS is a Unix or Unix-like system. 2049 // - the compiler being used, either "gc" or "gccgo" 2050 // - "cgo", if the cgo command is supported (see CGO_ENABLED in 2051 // 'go help environment'). 2052 // - a term for each Go major release, through the current version: 2053 // "go1.1" from Go version 1.1 onward, "go1.12" from Go 1.12, and so on. 2054 // - any additional tags given by the -tags flag (see 'go help build'). 2055 // 2056 // There are no separate build tags for beta or minor releases. 2057 // 2058 // If a file's name, after stripping the extension and a possible _test suffix, 2059 // matches any of the following patterns: 2060 // 2061 // *_GOOS 2062 // *_GOARCH 2063 // *_GOOS_GOARCH 2064 // 2065 // (example: source_windows_amd64.go) where GOOS and GOARCH represent 2066 // any known operating system and architecture values respectively, then 2067 // the file is considered to have an implicit build constraint requiring 2068 // those terms (in addition to any explicit constraints in the file). 2069 // 2070 // Using GOOS=android matches build tags and files as for GOOS=linux 2071 // in addition to android tags and files. 2072 // 2073 // Using GOOS=illumos matches build tags and files as for GOOS=solaris 2074 // in addition to illumos tags and files. 2075 // 2076 // Using GOOS=ios matches build tags and files as for GOOS=darwin 2077 // in addition to ios tags and files. 2078 // 2079 // The defined architecture feature build tags are: 2080 // 2081 // - For GOARCH=386, GO386=387 and GO386=sse2 2082 // set the 386.387 and 386.sse2 build tags, respectively. 2083 // - For GOARCH=amd64, GOAMD64=v1, v2, and v3 2084 // correspond to the amd64.v1, amd64.v2, and amd64.v3 feature build tags. 2085 // - For GOARCH=arm, GOARM=5, 6, and 7 2086 // correspond to the arm.5, arm.6, and arm.7 feature build tags. 2087 // - For GOARCH=arm64, GOARM64=v8.{0-9} and v9.{0-5} 2088 // correspond to the arm64.v8.{0-9} and arm64.v9.{0-5} feature build tags. 2089 // - For GOARCH=mips or mipsle, 2090 // GOMIPS=hardfloat and softfloat 2091 // correspond to the mips.hardfloat and mips.softfloat 2092 // (or mipsle.hardfloat and mipsle.softfloat) feature build tags. 2093 // - For GOARCH=mips64 or mips64le, 2094 // GOMIPS64=hardfloat and softfloat 2095 // correspond to the mips64.hardfloat and mips64.softfloat 2096 // (or mips64le.hardfloat and mips64le.softfloat) feature build tags. 2097 // - For GOARCH=ppc64 or ppc64le, 2098 // GOPPC64=power8, power9, and power10 correspond to the 2099 // ppc64.power8, ppc64.power9, and ppc64.power10 2100 // (or ppc64le.power8, ppc64le.power9, and ppc64le.power10) 2101 // feature build tags. 2102 // - For GOARCH=riscv64, 2103 // GORISCV64=rva20u64 and rva22u64 correspond to the riscv64.rva20u64 2104 // and riscv64.rva22u64 build tags. 2105 // - For GOARCH=wasm, GOWASM=satconv and signext 2106 // correspond to the wasm.satconv and wasm.signext feature build tags. 2107 // 2108 // For GOARCH=amd64, arm, ppc64, ppc64le, and riscv64, a particular feature level 2109 // sets the feature build tags for all previous levels as well. 2110 // For example, GOAMD64=v2 sets the amd64.v1 and amd64.v2 feature flags. 2111 // This ensures that code making use of v2 features continues to compile 2112 // when, say, GOAMD64=v4 is introduced. 2113 // Code handling the absence of a particular feature level 2114 // should use a negation: 2115 // 2116 // //go:build !amd64.v2 2117 // 2118 // To keep a file from being considered for any build: 2119 // 2120 // //go:build ignore 2121 // 2122 // (Any other unsatisfied word will work as well, but "ignore" is conventional.) 2123 // 2124 // To build a file only when using cgo, and only on Linux and OS X: 2125 // 2126 // //go:build cgo && (linux || darwin) 2127 // 2128 // Such a file is usually paired with another file implementing the 2129 // default functionality for other systems, which in this case would 2130 // carry the constraint: 2131 // 2132 // //go:build !(cgo && (linux || darwin)) 2133 // 2134 // Naming a file dns_windows.go will cause it to be included only when 2135 // building the package for Windows; similarly, math_386.s will be included 2136 // only when building the package for 32-bit x86. 2137 // 2138 // Go versions 1.16 and earlier used a different syntax for build constraints, 2139 // with a "// +build" prefix. The gofmt command will add an equivalent //go:build 2140 // constraint when encountering the older syntax. 2141 // 2142 // In modules with a Go version of 1.21 or later, if a file's build constraint 2143 // has a term for a Go major release, the language version used when compiling 2144 // the file will be the minimum version implied by the build constraint. 2145 // 2146 // # Build -json encoding 2147 // 2148 // The 'go build', 'go install', and 'go test' commands take a -json flag that 2149 // reports build output and failures as structured JSON output on standard 2150 // output. 2151 // 2152 // The JSON stream is a newline-separated sequence of BuildEvent objects 2153 // corresponding to the Go struct: 2154 // 2155 // type BuildEvent struct { 2156 // ImportPath string 2157 // Action string 2158 // Output string 2159 // } 2160 // 2161 // The ImportPath field gives the package ID of the package being built. 2162 // This matches the Package.ImportPath field of go list -json and the 2163 // TestEvent.FailedBuild field of go test -json. Note that it does not 2164 // match TestEvent.Package. 2165 // 2166 // The Action field is one of the following: 2167 // 2168 // build-output - The toolchain printed output 2169 // build-fail - The build failed 2170 // 2171 // The Output field is set for Action == "build-output" and is a portion of 2172 // the build's output. The concatenation of the Output fields of all output 2173 // events is the exact output of the build. A single event may contain one 2174 // or more lines of output and there may be more than one output event for 2175 // a given ImportPath. This matches the definition of the TestEvent.Output 2176 // field produced by go test -json. 2177 // 2178 // For go test -json, this struct is designed so that parsers can distinguish 2179 // interleaved TestEvents and BuildEvents by inspecting the Action field. 2180 // Furthermore, as with TestEvent, parsers can simply concatenate the Output 2181 // fields of all events to reconstruct the text format output, as it would 2182 // have appeared from go build without the -json flag. 2183 // 2184 // Note that there may also be non-JSON error text on standard error, even 2185 // with the -json flag. Typically, this indicates an early, serious error. 2186 // Consumers should be robust to this. 2187 // 2188 // # Build modes 2189 // 2190 // The 'go build' and 'go install' commands take a -buildmode argument which 2191 // indicates which kind of object file is to be built. Currently supported values 2192 // are: 2193 // 2194 // -buildmode=archive 2195 // Build the listed non-main packages into .a files. Packages named 2196 // main are ignored. 2197 // 2198 // -buildmode=c-archive 2199 // Build the listed main package, plus all packages it imports, 2200 // into a C archive file. The only callable symbols will be those 2201 // functions exported using a cgo //export comment. Requires 2202 // exactly one main package to be listed. 2203 // 2204 // -buildmode=c-shared 2205 // Build the listed main package, plus all packages it imports, 2206 // into a C shared library. The only callable symbols will 2207 // be those functions exported using a cgo //export comment. 2208 // On wasip1, this mode builds it to a WASI reactor/library, 2209 // of which the callable symbols are those functions exported 2210 // using a //go:wasmexport directive. Requires exactly one 2211 // main package to be listed. 2212 // 2213 // -buildmode=default 2214 // Listed main packages are built into executables and listed 2215 // non-main packages are built into .a files (the default 2216 // behavior). 2217 // 2218 // -buildmode=shared 2219 // Combine all the listed non-main packages into a single shared 2220 // library that will be used when building with the -linkshared 2221 // option. Packages named main are ignored. 2222 // 2223 // -buildmode=exe 2224 // Build the listed main packages and everything they import into 2225 // executables. Packages not named main are ignored. 2226 // 2227 // -buildmode=pie 2228 // Build the listed main packages and everything they import into 2229 // position independent executables (PIE). Packages not named 2230 // main are ignored. 2231 // 2232 // -buildmode=plugin 2233 // Build the listed main packages, plus all packages that they 2234 // import, into a Go plugin. Packages not named main are ignored. 2235 // 2236 // On AIX, when linking a C program that uses a Go archive built with 2237 // -buildmode=c-archive, you must pass -Wl,-bnoobjreorder to the C compiler. 2238 // 2239 // # Calling between Go and C 2240 // 2241 // There are two different ways to call between Go and C/C++ code. 2242 // 2243 // The first is the cgo tool, which is part of the Go distribution. For 2244 // information on how to use it see the cgo documentation (go doc cmd/cgo). 2245 // 2246 // The second is the SWIG program, which is a general tool for 2247 // interfacing between languages. For information on SWIG see 2248 // https://swig.org/. When running go build, any file with a .swig 2249 // extension will be passed to SWIG. Any file with a .swigcxx extension 2250 // will be passed to SWIG with the -c++ option. 2251 // 2252 // When either cgo or SWIG is used, go build will pass any .c, .m, .s, .S 2253 // or .sx files to the C compiler, and any .cc, .cpp, .cxx files to the C++ 2254 // compiler. The CC or CXX environment variables may be set to determine 2255 // the C or C++ compiler, respectively, to use. 2256 // 2257 // # Build and test caching 2258 // 2259 // The go command caches build outputs for reuse in future builds. 2260 // The default location for cache data is a subdirectory named go-build 2261 // in the standard user cache directory for the current operating system. 2262 // The cache is safe for concurrent invocations of the go command. 2263 // Setting the GOCACHE environment variable overrides this default, 2264 // and running 'go env GOCACHE' prints the current cache directory. 2265 // 2266 // The go command periodically deletes cached data that has not been 2267 // used recently. Running 'go clean -cache' deletes all cached data. 2268 // 2269 // The build cache correctly accounts for changes to Go source files, 2270 // compilers, compiler options, and so on: cleaning the cache explicitly 2271 // should not be necessary in typical use. However, the build cache 2272 // does not detect changes to C libraries imported with cgo. 2273 // If you have made changes to the C libraries on your system, you 2274 // will need to clean the cache explicitly or else use the -a build flag 2275 // (see 'go help build') to force rebuilding of packages that 2276 // depend on the updated C libraries. 2277 // 2278 // The go command also caches successful package test results. 2279 // See 'go help test' for details. Running 'go clean -testcache' removes 2280 // all cached test results (but not cached build results). 2281 // 2282 // The go command also caches values used in fuzzing with 'go test -fuzz', 2283 // specifically, values that expanded code coverage when passed to a 2284 // fuzz function. These values are not used for regular building and 2285 // testing, but they're stored in a subdirectory of the build cache. 2286 // Running 'go clean -fuzzcache' removes all cached fuzzing values. 2287 // This may make fuzzing less effective, temporarily. 2288 // 2289 // The GODEBUG environment variable can enable printing of debugging 2290 // information about the state of the cache: 2291 // 2292 // GODEBUG=gocacheverify=1 causes the go command to bypass the 2293 // use of any cache entries and instead rebuild everything and check 2294 // that the results match existing cache entries. 2295 // 2296 // GODEBUG=gocachehash=1 causes the go command to print the inputs 2297 // for all of the content hashes it uses to construct cache lookup keys. 2298 // The output is voluminous but can be useful for debugging the cache. 2299 // 2300 // GODEBUG=gocachetest=1 causes the go command to print details of its 2301 // decisions about whether to reuse a cached test result. 2302 // 2303 // # Environment variables 2304 // 2305 // The go command and the tools it invokes consult environment variables 2306 // for configuration. If an environment variable is unset or empty, the go 2307 // command uses a sensible default setting. To see the effective setting of 2308 // the variable <NAME>, run 'go env <NAME>'. To change the default setting, 2309 // run 'go env -w <NAME>=<VALUE>'. Defaults changed using 'go env -w' 2310 // are recorded in a Go environment configuration file stored in the 2311 // per-user configuration directory, as reported by os.UserConfigDir. 2312 // The location of the configuration file can be changed by setting 2313 // the environment variable GOENV, and 'go env GOENV' prints the 2314 // effective location, but 'go env -w' cannot change the default location. 2315 // See 'go help env' for details. 2316 // 2317 // General-purpose environment variables: 2318 // 2319 // GCCGO 2320 // The gccgo command to run for 'go build -compiler=gccgo'. 2321 // GO111MODULE 2322 // Controls whether the go command runs in module-aware mode or GOPATH mode. 2323 // May be "off", "on", or "auto". 2324 // See https://golang.org/ref/mod#mod-commands. 2325 // GOARCH 2326 // The architecture, or processor, for which to compile code. 2327 // Examples are amd64, 386, arm, ppc64. 2328 // GOAUTH 2329 // Controls authentication for go-import and HTTPS module mirror interactions. 2330 // See 'go help goauth'. 2331 // GOBIN 2332 // The directory where 'go install' will install a command. 2333 // GOCACHE 2334 // The directory where the go command will store cached 2335 // information for reuse in future builds. 2336 // GOCACHEPROG 2337 // A command (with optional space-separated flags) that implements an 2338 // external go command build cache. 2339 // See 'go doc cmd/go/internal/cacheprog'. 2340 // GODEBUG 2341 // Enable various debugging facilities for programs built with Go, 2342 // including the go command. Cannot be set using 'go env -w'. 2343 // See https://go.dev/doc/godebug for details. 2344 // GOENV 2345 // The location of the Go environment configuration file. 2346 // Cannot be set using 'go env -w'. 2347 // Setting GOENV=off in the environment disables the use of the 2348 // default configuration file. 2349 // GOFLAGS 2350 // A space-separated list of -flag=value settings to apply 2351 // to go commands by default, when the given flag is known by 2352 // the current command. Each entry must be a standalone flag. 2353 // Because the entries are space-separated, flag values must 2354 // not contain spaces. Flags listed on the command line 2355 // are applied after this list and therefore override it. 2356 // GOINSECURE 2357 // Comma-separated list of glob patterns (in the syntax of Go's path.Match) 2358 // of module path prefixes that should always be fetched in an insecure 2359 // manner. Only applies to dependencies that are being fetched directly. 2360 // GOINSECURE does not disable checksum database validation. GOPRIVATE or 2361 // GONOSUMDB may be used to achieve that. 2362 // GOMODCACHE 2363 // The directory where the go command will store downloaded modules. 2364 // GOOS 2365 // The operating system for which to compile code. 2366 // Examples are linux, darwin, windows, netbsd. 2367 // GOPATH 2368 // Controls where various files are stored. See: 'go help gopath'. 2369 // GOPRIVATE, GONOPROXY, GONOSUMDB 2370 // Comma-separated list of glob patterns (in the syntax of Go's path.Match) 2371 // of module path prefixes that should always be fetched directly 2372 // or that should not be compared against the checksum database. 2373 // See https://golang.org/ref/mod#private-modules. 2374 // GOPROXY 2375 // URL of Go module proxy. See https://golang.org/ref/mod#environment-variables 2376 // and https://golang.org/ref/mod#module-proxy for details. 2377 // GOROOT 2378 // The root of the go tree. 2379 // GOSUMDB 2380 // The name of checksum database to use and optionally its public key and 2381 // URL. See https://golang.org/ref/mod#authenticating. 2382 // GOTMPDIR 2383 // The directory where the go command will write 2384 // temporary source files, packages, and binaries. 2385 // GOTOOLCHAIN 2386 // Controls which Go toolchain is used. See https://go.dev/doc/toolchain. 2387 // GOVCS 2388 // Lists version control commands that may be used with matching servers. 2389 // See 'go help vcs'. 2390 // GOWORK 2391 // In module aware mode, use the given go.work file as a workspace file. 2392 // By default or when GOWORK is "auto", the go command searches for a 2393 // file named go.work in the current directory and then containing directories 2394 // until one is found. If a valid go.work file is found, the modules 2395 // specified will collectively be used as the main modules. If GOWORK 2396 // is "off", or a go.work file is not found in "auto" mode, workspace 2397 // mode is disabled. 2398 // 2399 // Environment variables for use with cgo: 2400 // 2401 // AR 2402 // The command to use to manipulate library archives when 2403 // building with the gccgo compiler. 2404 // The default is 'ar'. 2405 // CC 2406 // The command to use to compile C code. 2407 // CGO_CFLAGS 2408 // Flags that cgo will pass to the compiler when compiling 2409 // C code. 2410 // CGO_CFLAGS_ALLOW 2411 // A regular expression specifying additional flags to allow 2412 // to appear in #cgo CFLAGS source code directives. 2413 // Does not apply to the CGO_CFLAGS environment variable. 2414 // CGO_CFLAGS_DISALLOW 2415 // A regular expression specifying flags that must be disallowed 2416 // from appearing in #cgo CFLAGS source code directives. 2417 // Does not apply to the CGO_CFLAGS environment variable. 2418 // CGO_CPPFLAGS, CGO_CPPFLAGS_ALLOW, CGO_CPPFLAGS_DISALLOW 2419 // Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW, 2420 // but for the C preprocessor. 2421 // CGO_CXXFLAGS, CGO_CXXFLAGS_ALLOW, CGO_CXXFLAGS_DISALLOW 2422 // Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW, 2423 // but for the C++ compiler. 2424 // CGO_ENABLED 2425 // Whether the cgo command is supported. Either 0 or 1. 2426 // CGO_FFLAGS, CGO_FFLAGS_ALLOW, CGO_FFLAGS_DISALLOW 2427 // Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW, 2428 // but for the Fortran compiler. 2429 // CGO_LDFLAGS, CGO_LDFLAGS_ALLOW, CGO_LDFLAGS_DISALLOW 2430 // Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW, 2431 // but for the linker. 2432 // CXX 2433 // The command to use to compile C++ code. 2434 // FC 2435 // The command to use to compile Fortran code. 2436 // PKG_CONFIG 2437 // Path to pkg-config tool. 2438 // 2439 // Architecture-specific environment variables: 2440 // 2441 // GO386 2442 // For GOARCH=386, how to implement floating point instructions. 2443 // Valid values are sse2 (default), softfloat. 2444 // GOAMD64 2445 // For GOARCH=amd64, the microarchitecture level for which to compile. 2446 // Valid values are v1 (default), v2, v3, v4. 2447 // See https://golang.org/wiki/MinimumRequirements#amd64 2448 // GOARM 2449 // For GOARCH=arm, the ARM architecture for which to compile. 2450 // Valid values are 5, 6, 7. 2451 // When the Go tools are built on an arm system, 2452 // the default value is set based on what the build system supports. 2453 // When the Go tools are not built on an arm system 2454 // (that is, when building a cross-compiler), 2455 // the default value is 7. 2456 // The value can be followed by an option specifying how to implement floating point instructions. 2457 // Valid options are ,softfloat (default for 5) and ,hardfloat (default for 6 and 7). 2458 // GOARM64 2459 // For GOARCH=arm64, the ARM64 architecture for which to compile. 2460 // Valid values are v8.0 (default), v8.{1-9}, v9.{0-5}. 2461 // The value can be followed by an option specifying extensions implemented by target hardware. 2462 // Valid options are ,lse and ,crypto. 2463 // Note that some extensions are enabled by default starting from a certain GOARM64 version; 2464 // for example, lse is enabled by default starting from v8.1. 2465 // GOMIPS 2466 // For GOARCH=mips{,le}, whether to use floating point instructions. 2467 // Valid values are hardfloat (default), softfloat. 2468 // GOMIPS64 2469 // For GOARCH=mips64{,le}, whether to use floating point instructions. 2470 // Valid values are hardfloat (default), softfloat. 2471 // GOPPC64 2472 // For GOARCH=ppc64{,le}, the target ISA (Instruction Set Architecture). 2473 // Valid values are power8 (default), power9, power10. 2474 // GORISCV64 2475 // For GOARCH=riscv64, the RISC-V user-mode application profile for which 2476 // to compile. Valid values are rva20u64 (default), rva22u64. 2477 // See https://github.com/riscv/riscv-profiles/blob/main/src/profiles.adoc 2478 // GOWASM 2479 // For GOARCH=wasm, comma-separated list of experimental WebAssembly features to use. 2480 // Valid values are satconv, signext. 2481 // 2482 // Environment variables for use with code coverage: 2483 // 2484 // GOCOVERDIR 2485 // Directory into which to write code coverage data files 2486 // generated by running a "go build -cover" binary. 2487 // Requires that GOEXPERIMENT=coverageredesign is enabled. 2488 // 2489 // Special-purpose environment variables: 2490 // 2491 // GCCGOTOOLDIR 2492 // If set, where to find gccgo tools, such as cgo. 2493 // The default is based on how gccgo was configured. 2494 // GOEXPERIMENT 2495 // Comma-separated list of toolchain experiments to enable or disable. 2496 // The list of available experiments may change arbitrarily over time. 2497 // See GOROOT/src/internal/goexperiment/flags.go for currently valid values. 2498 // Warning: This variable is provided for the development and testing 2499 // of the Go toolchain itself. Use beyond that purpose is unsupported. 2500 // GOFIPS140 2501 // The FIPS-140 cryptography mode to use when building binaries. 2502 // The default is GOFIPS140=off, which makes no FIPS-140 changes at all. 2503 // Other values enable FIPS-140 compliance measures and select alternate 2504 // versions of the cryptography source code. 2505 // See https://go.dev/security/fips140 for details. 2506 // GO_EXTLINK_ENABLED 2507 // Whether the linker should use external linking mode 2508 // when using -linkmode=auto with code that uses cgo. 2509 // Set to 0 to disable external linking mode, 1 to enable it. 2510 // GIT_ALLOW_PROTOCOL 2511 // Defined by Git. A colon-separated list of schemes that are allowed 2512 // to be used with git fetch/clone. If set, any scheme not explicitly 2513 // mentioned will be considered insecure by 'go get'. 2514 // Because the variable is defined by Git, the default value cannot 2515 // be set using 'go env -w'. 2516 // 2517 // Additional information available from 'go env' but not read from the environment: 2518 // 2519 // GOEXE 2520 // The executable file name suffix (".exe" on Windows, "" on other systems). 2521 // GOGCCFLAGS 2522 // A space-separated list of arguments supplied to the CC command. 2523 // GOHOSTARCH 2524 // The architecture (GOARCH) of the Go toolchain binaries. 2525 // GOHOSTOS 2526 // The operating system (GOOS) of the Go toolchain binaries. 2527 // GOMOD 2528 // The absolute path to the go.mod of the main module. 2529 // If module-aware mode is enabled, but there is no go.mod, GOMOD will be 2530 // os.DevNull ("/dev/null" on Unix-like systems, "NUL" on Windows). 2531 // If module-aware mode is disabled, GOMOD will be the empty string. 2532 // GOTELEMETRY 2533 // The current Go telemetry mode ("off", "local", or "on"). 2534 // See "go help telemetry" for more information. 2535 // GOTELEMETRYDIR 2536 // The directory Go telemetry data is written is written to. 2537 // GOTOOLDIR 2538 // The directory where the go tools (compile, cover, doc, etc...) are installed. 2539 // GOVERSION 2540 // The version of the installed Go tree, as reported by runtime.Version. 2541 // 2542 // # File types 2543 // 2544 // The go command examines the contents of a restricted set of files 2545 // in each directory. It identifies which files to examine based on 2546 // the extension of the file name. These extensions are: 2547 // 2548 // .go 2549 // Go source files. 2550 // .c, .h 2551 // C source files. 2552 // If the package uses cgo or SWIG, these will be compiled with the 2553 // OS-native compiler (typically gcc); otherwise they will 2554 // trigger an error. 2555 // .cc, .cpp, .cxx, .hh, .hpp, .hxx 2556 // C++ source files. Only useful with cgo or SWIG, and always 2557 // compiled with the OS-native compiler. 2558 // .m 2559 // Objective-C source files. Only useful with cgo, and always 2560 // compiled with the OS-native compiler. 2561 // .s, .S, .sx 2562 // Assembler source files. 2563 // If the package uses cgo or SWIG, these will be assembled with the 2564 // OS-native assembler (typically gcc (sic)); otherwise they 2565 // will be assembled with the Go assembler. 2566 // .swig, .swigcxx 2567 // SWIG definition files. 2568 // .syso 2569 // System object files. 2570 // 2571 // Files of each of these types except .syso may contain build 2572 // constraints, but the go command stops scanning for build constraints 2573 // at the first item in the file that is not a blank line or //-style 2574 // line comment. See the go/build package documentation for 2575 // more details. 2576 // 2577 // # GOAUTH environment variable 2578 // 2579 // GOAUTH is a semicolon-separated list of authentication commands for go-import and 2580 // HTTPS module mirror interactions. The default is netrc. 2581 // 2582 // The supported authentication commands are: 2583 // 2584 // off 2585 // 2586 // Disables authentication. 2587 // 2588 // netrc 2589 // 2590 // Uses credentials from NETRC or the .netrc file in your home directory. 2591 // 2592 // git dir 2593 // 2594 // Runs 'git credential fill' in dir and uses its credentials. The 2595 // go command will run 'git credential approve/reject' to update 2596 // the credential helper's cache. 2597 // 2598 // command 2599 // 2600 // Executes the given command (a space-separated argument list) and attaches 2601 // the provided headers to HTTPS requests. 2602 // The command must produce output in the following format: 2603 // Response = { CredentialSet } . 2604 // CredentialSet = URLLine { URLLine } BlankLine { HeaderLine } BlankLine . 2605 // URLLine = /* URL that starts with "https://" */ '\n' . 2606 // HeaderLine = /* HTTP Request header */ '\n' . 2607 // BlankLine = '\n' . 2608 // 2609 // Example: 2610 // https://example.com/ 2611 // https://example.net/api/ 2612 // 2613 // Authorization: Basic <token> 2614 // 2615 // https://another-example.org/ 2616 // 2617 // Example: Data 2618 // 2619 // If the server responds with any 4xx code, the go command will write the 2620 // following to the program's stdin: 2621 // Response = StatusLine { HeaderLine } BlankLine . 2622 // StatusLine = Protocol Space Status '\n' . 2623 // Protocol = /* HTTP protocol */ . 2624 // Space = ' ' . 2625 // Status = /* HTTP status code */ . 2626 // BlankLine = '\n' . 2627 // HeaderLine = /* HTTP Response's header */ '\n' . 2628 // 2629 // Example: 2630 // HTTP/1.1 401 Unauthorized 2631 // Content-Length: 19 2632 // Content-Type: text/plain; charset=utf-8 2633 // Date: Thu, 07 Nov 2024 18:43:09 GMT 2634 // 2635 // Note: it is safe to use net/http.ReadResponse to parse this input. 2636 // 2637 // Before the first HTTPS fetch, the go command will invoke each GOAUTH 2638 // command in the list with no additional arguments and no input. 2639 // If the server responds with any 4xx code, the go command will invoke the 2640 // GOAUTH commands again with the URL as an additional command-line argument 2641 // and the HTTP Response to the program's stdin. 2642 // If the server responds with an error again, the fetch fails: a URL-specific 2643 // GOAUTH will only be attempted once per fetch. 2644 // 2645 // # The go.mod file 2646 // 2647 // A module version is defined by a tree of source files, with a go.mod 2648 // file in its root. When the go command is run, it looks in the current 2649 // directory and then successive parent directories to find the go.mod 2650 // marking the root of the main (current) module. 2651 // 2652 // The go.mod file format is described in detail at 2653 // https://golang.org/ref/mod#go-mod-file. 2654 // 2655 // To create a new go.mod file, use 'go mod init'. For details see 2656 // 'go help mod init' or https://golang.org/ref/mod#go-mod-init. 2657 // 2658 // To add missing module requirements or remove unneeded requirements, 2659 // use 'go mod tidy'. For details, see 'go help mod tidy' or 2660 // https://golang.org/ref/mod#go-mod-tidy. 2661 // 2662 // To add, upgrade, downgrade, or remove a specific module requirement, use 2663 // 'go get'. For details, see 'go help module-get' or 2664 // https://golang.org/ref/mod#go-get. 2665 // 2666 // To make other changes or to parse go.mod as JSON for use by other tools, 2667 // use 'go mod edit'. See 'go help mod edit' or 2668 // https://golang.org/ref/mod#go-mod-edit. 2669 // 2670 // # GOPATH environment variable 2671 // 2672 // The Go path is used to resolve import statements. 2673 // It is implemented by and documented in the go/build package. 2674 // 2675 // The GOPATH environment variable lists places to look for Go code. 2676 // On Unix, the value is a colon-separated string. 2677 // On Windows, the value is a semicolon-separated string. 2678 // On Plan 9, the value is a list. 2679 // 2680 // If the environment variable is unset, GOPATH defaults 2681 // to a subdirectory named "go" in the user's home directory 2682 // ($HOME/go on Unix, %USERPROFILE%\go on Windows), 2683 // unless that directory holds a Go distribution. 2684 // Run "go env GOPATH" to see the current GOPATH. 2685 // 2686 // See https://golang.org/wiki/SettingGOPATH to set a custom GOPATH. 2687 // 2688 // Each directory listed in GOPATH must have a prescribed structure: 2689 // 2690 // The src directory holds source code. The path below src 2691 // determines the import path or executable name. 2692 // 2693 // The pkg directory holds installed package objects. 2694 // As in the Go tree, each target operating system and 2695 // architecture pair has its own subdirectory of pkg 2696 // (pkg/GOOS_GOARCH). 2697 // 2698 // If DIR is a directory listed in the GOPATH, a package with 2699 // source in DIR/src/foo/bar can be imported as "foo/bar" and 2700 // has its compiled form installed to "DIR/pkg/GOOS_GOARCH/foo/bar.a". 2701 // 2702 // The bin directory holds compiled commands. 2703 // Each command is named for its source directory, but only 2704 // the final element, not the entire path. That is, the 2705 // command with source in DIR/src/foo/quux is installed into 2706 // DIR/bin/quux, not DIR/bin/foo/quux. The "foo/" prefix is stripped 2707 // so that you can add DIR/bin to your PATH to get at the 2708 // installed commands. If the GOBIN environment variable is 2709 // set, commands are installed to the directory it names instead 2710 // of DIR/bin. GOBIN must be an absolute path. 2711 // 2712 // Here's an example directory layout: 2713 // 2714 // GOPATH=/home/user/go 2715 // 2716 // /home/user/go/ 2717 // src/ 2718 // foo/ 2719 // bar/ (go code in package bar) 2720 // x.go 2721 // quux/ (go code in package main) 2722 // y.go 2723 // bin/ 2724 // quux (installed command) 2725 // pkg/ 2726 // linux_amd64/ 2727 // foo/ 2728 // bar.a (installed package object) 2729 // 2730 // Go searches each directory listed in GOPATH to find source code, 2731 // but new packages are always downloaded into the first directory 2732 // in the list. 2733 // 2734 // See https://golang.org/doc/code.html for an example. 2735 // 2736 // # GOPATH and Modules 2737 // 2738 // When using modules, GOPATH is no longer used for resolving imports. 2739 // However, it is still used to store downloaded source code (in GOPATH/pkg/mod) 2740 // and compiled commands (in GOPATH/bin). 2741 // 2742 // # Internal Directories 2743 // 2744 // Code in or below a directory named "internal" is importable only 2745 // by code in the directory tree rooted at the parent of "internal". 2746 // Here's an extended version of the directory layout above: 2747 // 2748 // /home/user/go/ 2749 // src/ 2750 // crash/ 2751 // bang/ (go code in package bang) 2752 // b.go 2753 // foo/ (go code in package foo) 2754 // f.go 2755 // bar/ (go code in package bar) 2756 // x.go 2757 // internal/ 2758 // baz/ (go code in package baz) 2759 // z.go 2760 // quux/ (go code in package main) 2761 // y.go 2762 // 2763 // The code in z.go is imported as "foo/internal/baz", but that 2764 // import statement can only appear in source files in the subtree 2765 // rooted at foo. The source files foo/f.go, foo/bar/x.go, and 2766 // foo/quux/y.go can all import "foo/internal/baz", but the source file 2767 // crash/bang/b.go cannot. 2768 // 2769 // See https://golang.org/s/go14internal for details. 2770 // 2771 // # Vendor Directories 2772 // 2773 // Go 1.6 includes support for using local copies of external dependencies 2774 // to satisfy imports of those dependencies, often referred to as vendoring. 2775 // 2776 // Code below a directory named "vendor" is importable only 2777 // by code in the directory tree rooted at the parent of "vendor", 2778 // and only using an import path that omits the prefix up to and 2779 // including the vendor element. 2780 // 2781 // Here's the example from the previous section, 2782 // but with the "internal" directory renamed to "vendor" 2783 // and a new foo/vendor/crash/bang directory added: 2784 // 2785 // /home/user/go/ 2786 // src/ 2787 // crash/ 2788 // bang/ (go code in package bang) 2789 // b.go 2790 // foo/ (go code in package foo) 2791 // f.go 2792 // bar/ (go code in package bar) 2793 // x.go 2794 // vendor/ 2795 // crash/ 2796 // bang/ (go code in package bang) 2797 // b.go 2798 // baz/ (go code in package baz) 2799 // z.go 2800 // quux/ (go code in package main) 2801 // y.go 2802 // 2803 // The same visibility rules apply as for internal, but the code 2804 // in z.go is imported as "baz", not as "foo/vendor/baz". 2805 // 2806 // Code in vendor directories deeper in the source tree shadows 2807 // code in higher directories. Within the subtree rooted at foo, an import 2808 // of "crash/bang" resolves to "foo/vendor/crash/bang", not the 2809 // top-level "crash/bang". 2810 // 2811 // Code in vendor directories is not subject to import path 2812 // checking (see 'go help importpath'). 2813 // 2814 // When 'go get' checks out or updates a git repository, it now also 2815 // updates submodules. 2816 // 2817 // Vendor directories do not affect the placement of new repositories 2818 // being checked out for the first time by 'go get': those are always 2819 // placed in the main GOPATH, never in a vendor subtree. 2820 // 2821 // See https://golang.org/s/go15vendor for details. 2822 // 2823 // # Module proxy protocol 2824 // 2825 // A Go module proxy is any web server that can respond to GET requests for 2826 // URLs of a specified form. The requests have no query parameters, so even 2827 // a site serving from a fixed file system (including a file:/// URL) 2828 // can be a module proxy. 2829 // 2830 // For details on the GOPROXY protocol, see 2831 // https://golang.org/ref/mod#goproxy-protocol. 2832 // 2833 // # Import path syntax 2834 // 2835 // An import path (see 'go help packages') denotes a package stored in the local 2836 // file system. In general, an import path denotes either a standard package (such 2837 // as "unicode/utf8") or a package found in one of the work spaces (For more 2838 // details see: 'go help gopath'). 2839 // 2840 // # Relative import paths 2841 // 2842 // An import path beginning with ./ or ../ is called a relative path. 2843 // The toolchain supports relative import paths as a shortcut in two ways. 2844 // 2845 // First, a relative path can be used as a shorthand on the command line. 2846 // If you are working in the directory containing the code imported as 2847 // "unicode" and want to run the tests for "unicode/utf8", you can type 2848 // "go test ./utf8" instead of needing to specify the full path. 2849 // Similarly, in the reverse situation, "go test .." will test "unicode" from 2850 // the "unicode/utf8" directory. Relative patterns are also allowed, like 2851 // "go test ./..." to test all subdirectories. See 'go help packages' for details 2852 // on the pattern syntax. 2853 // 2854 // Second, if you are compiling a Go program not in a work space, 2855 // you can use a relative path in an import statement in that program 2856 // to refer to nearby code also not in a work space. 2857 // This makes it easy to experiment with small multipackage programs 2858 // outside of the usual work spaces, but such programs cannot be 2859 // installed with "go install" (there is no work space in which to install them), 2860 // so they are rebuilt from scratch each time they are built. 2861 // To avoid ambiguity, Go programs cannot use relative import paths 2862 // within a work space. 2863 // 2864 // # Remote import paths 2865 // 2866 // Certain import paths also 2867 // describe how to obtain the source code for the package using 2868 // a revision control system. 2869 // 2870 // A few common code hosting sites have special syntax: 2871 // 2872 // Bitbucket (Git, Mercurial) 2873 // 2874 // import "bitbucket.org/user/project" 2875 // import "bitbucket.org/user/project/sub/directory" 2876 // 2877 // GitHub (Git) 2878 // 2879 // import "github.com/user/project" 2880 // import "github.com/user/project/sub/directory" 2881 // 2882 // Launchpad (Bazaar) 2883 // 2884 // import "launchpad.net/project" 2885 // import "launchpad.net/project/series" 2886 // import "launchpad.net/project/series/sub/directory" 2887 // 2888 // import "launchpad.net/~user/project/branch" 2889 // import "launchpad.net/~user/project/branch/sub/directory" 2890 // 2891 // IBM DevOps Services (Git) 2892 // 2893 // import "hub.jazz.net/git/user/project" 2894 // import "hub.jazz.net/git/user/project/sub/directory" 2895 // 2896 // For code hosted on other servers, import paths may either be qualified 2897 // with the version control type, or the go tool can dynamically fetch 2898 // the import path over https/http and discover where the code resides 2899 // from a <meta> tag in the HTML. 2900 // 2901 // To declare the code location, an import path of the form 2902 // 2903 // repository.vcs/path 2904 // 2905 // specifies the given repository, with or without the .vcs suffix, 2906 // using the named version control system, and then the path inside 2907 // that repository. The supported version control systems are: 2908 // 2909 // Bazaar .bzr 2910 // Fossil .fossil 2911 // Git .git 2912 // Mercurial .hg 2913 // Subversion .svn 2914 // 2915 // For example, 2916 // 2917 // import "example.org/user/foo.hg" 2918 // 2919 // denotes the root directory of the Mercurial repository at 2920 // example.org/user/foo or foo.hg, and 2921 // 2922 // import "example.org/repo.git/foo/bar" 2923 // 2924 // denotes the foo/bar directory of the Git repository at 2925 // example.org/repo or repo.git. 2926 // 2927 // When a version control system supports multiple protocols, 2928 // each is tried in turn when downloading. For example, a Git 2929 // download tries https://, then git+ssh://. 2930 // 2931 // By default, downloads are restricted to known secure protocols 2932 // (e.g. https, ssh). To override this setting for Git downloads, the 2933 // GIT_ALLOW_PROTOCOL environment variable can be set (For more details see: 2934 // 'go help environment'). 2935 // 2936 // If the import path is not a known code hosting site and also lacks a 2937 // version control qualifier, the go tool attempts to fetch the import 2938 // over https/http and looks for a <meta> tag in the document's HTML 2939 // <head>. 2940 // 2941 // The meta tag has the form: 2942 // 2943 // <meta name="go-import" content="import-prefix vcs repo-root"> 2944 // 2945 // The import-prefix is the import path corresponding to the repository 2946 // root. It must be a prefix or an exact match of the package being 2947 // fetched with "go get". If it's not an exact match, another http 2948 // request is made at the prefix to verify the <meta> tags match. 2949 // 2950 // The meta tag should appear as early in the file as possible. 2951 // In particular, it should appear before any raw JavaScript or CSS, 2952 // to avoid confusing the go command's restricted parser. 2953 // 2954 // The vcs is one of "bzr", "fossil", "git", "hg", "svn". 2955 // 2956 // The repo-root is the root of the version control system 2957 // containing a scheme and not containing a .vcs qualifier. 2958 // 2959 // For example, 2960 // 2961 // import "example.org/pkg/foo" 2962 // 2963 // will result in the following requests: 2964 // 2965 // https://example.org/pkg/foo?go-get=1 (preferred) 2966 // http://example.org/pkg/foo?go-get=1 (fallback, only with use of correctly set GOINSECURE) 2967 // 2968 // If that page contains the meta tag 2969 // 2970 // <meta name="go-import" content="example.org git https://code.org/r/p/exproj"> 2971 // 2972 // the go tool will verify that https://example.org/?go-get=1 contains the 2973 // same meta tag and then git clone https://code.org/r/p/exproj into 2974 // GOPATH/src/example.org. 2975 // 2976 // Downloaded packages are stored in the module cache. 2977 // See https://golang.org/ref/mod#module-cache. 2978 // 2979 // When using modules, an additional variant of the go-import meta tag is 2980 // recognized and is preferred over those listing version control systems. 2981 // That variant uses "mod" as the vcs in the content value, as in: 2982 // 2983 // <meta name="go-import" content="example.org mod https://code.org/moduleproxy"> 2984 // 2985 // This tag means to fetch modules with paths beginning with example.org 2986 // from the module proxy available at the URL https://code.org/moduleproxy. 2987 // See https://golang.org/ref/mod#goproxy-protocol for details about the 2988 // proxy protocol. 2989 // 2990 // # Import path checking 2991 // 2992 // When the custom import path feature described above redirects to a 2993 // known code hosting site, each of the resulting packages has two possible 2994 // import paths, using the custom domain or the known hosting site. 2995 // 2996 // A package statement is said to have an "import comment" if it is immediately 2997 // followed (before the next newline) by a comment of one of these two forms: 2998 // 2999 // package math // import "path" 3000 // package math /* import "path" */ 3001 // 3002 // The go command will refuse to install a package with an import comment 3003 // unless it is being referred to by that import path. In this way, import comments 3004 // let package authors make sure the custom import path is used and not a 3005 // direct path to the underlying code hosting site. 3006 // 3007 // Import path checking is disabled for code found within vendor trees. 3008 // This makes it possible to copy code into alternate locations in vendor trees 3009 // without needing to update import comments. 3010 // 3011 // Import path checking is also disabled when using modules. 3012 // Import path comments are obsoleted by the go.mod file's module statement. 3013 // 3014 // See https://golang.org/s/go14customimport for details. 3015 // 3016 // # Modules, module versions, and more 3017 // 3018 // Modules are how Go manages dependencies. 3019 // 3020 // A module is a collection of packages that are released, versioned, and 3021 // distributed together. Modules may be downloaded directly from version control 3022 // repositories or from module proxy servers. 3023 // 3024 // For a series of tutorials on modules, see 3025 // https://golang.org/doc/tutorial/create-module. 3026 // 3027 // For a detailed reference on modules, see https://golang.org/ref/mod. 3028 // 3029 // By default, the go command may download modules from https://proxy.golang.org. 3030 // It may authenticate modules using the checksum database at 3031 // https://sum.golang.org. Both services are operated by the Go team at Google. 3032 // The privacy policies for these services are available at 3033 // https://proxy.golang.org/privacy and https://sum.golang.org/privacy, 3034 // respectively. 3035 // 3036 // The go command's download behavior may be configured using GOPROXY, GOSUMDB, 3037 // GOPRIVATE, and other environment variables. See 'go help environment' 3038 // and https://golang.org/ref/mod#private-module-privacy for more information. 3039 // 3040 // # Module authentication using go.sum 3041 // 3042 // When the go command downloads a module zip file or go.mod file into the 3043 // module cache, it computes a cryptographic hash and compares it with a known 3044 // value to verify the file hasn't changed since it was first downloaded. Known 3045 // hashes are stored in a file in the module root directory named go.sum. Hashes 3046 // may also be downloaded from the checksum database depending on the values of 3047 // GOSUMDB, GOPRIVATE, and GONOSUMDB. 3048 // 3049 // For details, see https://golang.org/ref/mod#authenticating. 3050 // 3051 // # Package lists and patterns 3052 // 3053 // Many commands apply to a set of packages: 3054 // 3055 // go <action> [packages] 3056 // 3057 // Usually, [packages] is a list of import paths. 3058 // 3059 // An import path that is a rooted path or that begins with 3060 // a . or .. element is interpreted as a file system path and 3061 // denotes the package in that directory. 3062 // 3063 // Otherwise, the import path P denotes the package found in 3064 // the directory DIR/src/P for some DIR listed in the GOPATH 3065 // environment variable (For more details see: 'go help gopath'). 3066 // 3067 // If no import paths are given, the action applies to the 3068 // package in the current directory. 3069 // 3070 // There are five reserved names for paths that should not be used 3071 // for packages to be built with the go tool: 3072 // 3073 // - "main" denotes the top-level package in a stand-alone executable. 3074 // 3075 // - "all" expands to all packages in the main module (or workspace modules) and 3076 // their dependencies, including dependencies needed by tests of any of those. In 3077 // GOPATH mode, "all" expands to all packages found in all the GOPATH trees. 3078 // 3079 // - "std" is like all but expands to just the packages in the standard 3080 // Go library. 3081 // 3082 // - "cmd" expands to the Go repository's commands and their 3083 // internal libraries. 3084 // 3085 // - "tool" expands to the tools defined in the current module's go.mod file. 3086 // 3087 // Package names match against fully-qualified import paths or patterns that 3088 // match against any number of import paths. For instance, "fmt" refers to the 3089 // standard library's package fmt, but "http" alone for package http would not 3090 // match the import path "net/http" from the standard library. Instead, the 3091 // complete import path "net/http" must be used. 3092 // 3093 // Import paths beginning with "cmd/" only match source code in 3094 // the Go repository. 3095 // 3096 // An import path is a pattern if it includes one or more "..." wildcards, 3097 // each of which can match any string, including the empty string and 3098 // strings containing slashes. Such a pattern expands to all package 3099 // directories found in the GOPATH trees with names matching the 3100 // patterns. 3101 // 3102 // To make common patterns more convenient, there are two special cases. 3103 // First, /... at the end of the pattern can match an empty string, 3104 // so that net/... matches both net and packages in its subdirectories, like net/http. 3105 // Second, any slash-separated pattern element containing a wildcard never 3106 // participates in a match of the "vendor" element in the path of a vendored 3107 // package, so that ./... does not match packages in subdirectories of 3108 // ./vendor or ./mycode/vendor, but ./vendor/... and ./mycode/vendor/... do. 3109 // Note, however, that a directory named vendor that itself contains code 3110 // is not a vendored package: cmd/vendor would be a command named vendor, 3111 // and the pattern cmd/... matches it. 3112 // See golang.org/s/go15vendor for more about vendoring. 3113 // 3114 // An import path can also name a package to be downloaded from 3115 // a remote repository. Run 'go help importpath' for details. 3116 // 3117 // Every package in a program must have a unique import path. 3118 // By convention, this is arranged by starting each path with a 3119 // unique prefix that belongs to you. For example, paths used 3120 // internally at Google all begin with 'google', and paths 3121 // denoting remote repositories begin with the path to the code, 3122 // such as 'github.com/user/repo'. Package patterns should include this prefix. 3123 // For instance, a package called 'http' residing under 'github.com/user/repo', 3124 // would be addressed with the fully-qualified pattern: 3125 // 'github.com/user/repo/http'. 3126 // 3127 // Packages in a program need not have unique package names, 3128 // but there are two reserved package names with special meaning. 3129 // The name main indicates a command, not a library. 3130 // Commands are built into binaries and cannot be imported. 3131 // The name documentation indicates documentation for 3132 // a non-Go program in the directory. Files in package documentation 3133 // are ignored by the go command. 3134 // 3135 // As a special case, if the package list is a list of .go files from a 3136 // single directory, the command is applied to a single synthesized 3137 // package made up of exactly those files, ignoring any build constraints 3138 // in those files and ignoring any other files in the directory. 3139 // 3140 // Directory and file names that begin with "." or "_" are ignored 3141 // by the go tool, as are directories named "testdata". 3142 // 3143 // # Configuration for downloading non-public code 3144 // 3145 // The go command defaults to downloading modules from the public Go module 3146 // mirror at proxy.golang.org. It also defaults to validating downloaded modules, 3147 // regardless of source, against the public Go checksum database at sum.golang.org. 3148 // These defaults work well for publicly available source code. 3149 // 3150 // The GOPRIVATE environment variable controls which modules the go command 3151 // considers to be private (not available publicly) and should therefore not use 3152 // the proxy or checksum database. The variable is a comma-separated list of 3153 // glob patterns (in the syntax of Go's path.Match) of module path prefixes. 3154 // For example, 3155 // 3156 // GOPRIVATE=*.corp.example.com,rsc.io/private 3157 // 3158 // causes the go command to treat as private any module with a path prefix 3159 // matching either pattern, including git.corp.example.com/xyzzy, rsc.io/private, 3160 // and rsc.io/private/quux. 3161 // 3162 // For fine-grained control over module download and validation, the GONOPROXY 3163 // and GONOSUMDB environment variables accept the same kind of glob list 3164 // and override GOPRIVATE for the specific decision of whether to use the proxy 3165 // and checksum database, respectively. 3166 // 3167 // For example, if a company ran a module proxy serving private modules, 3168 // users would configure go using: 3169 // 3170 // GOPRIVATE=*.corp.example.com 3171 // GOPROXY=proxy.example.com 3172 // GONOPROXY=none 3173 // 3174 // The GOPRIVATE variable is also used to define the "public" and "private" 3175 // patterns for the GOVCS variable; see 'go help vcs'. For that usage, 3176 // GOPRIVATE applies even in GOPATH mode. In that case, it matches import paths 3177 // instead of module paths. 3178 // 3179 // The 'go env -w' command (see 'go help env') can be used to set these variables 3180 // for future go command invocations. 3181 // 3182 // For more details, see https://golang.org/ref/mod#private-modules. 3183 // 3184 // # Testing flags 3185 // 3186 // The 'go test' command takes both flags that apply to 'go test' itself 3187 // and flags that apply to the resulting test binary. 3188 // 3189 // Several of the flags control profiling and write an execution profile 3190 // suitable for "go tool pprof"; run "go tool pprof -h" for more 3191 // information. The --alloc_space, --alloc_objects, and --show_bytes 3192 // options of pprof control how the information is presented. 3193 // 3194 // The following flags are recognized by the 'go test' command and 3195 // control the execution of any test: 3196 // 3197 // -bench regexp 3198 // Run only those benchmarks matching a regular expression. 3199 // By default, no benchmarks are run. 3200 // To run all benchmarks, use '-bench .' or '-bench=.'. 3201 // The regular expression is split by unbracketed slash (/) 3202 // characters into a sequence of regular expressions, and each 3203 // part of a benchmark's identifier must match the corresponding 3204 // element in the sequence, if any. Possible parents of matches 3205 // are run with b.N=1 to identify sub-benchmarks. For example, 3206 // given -bench=X/Y, top-level benchmarks matching X are run 3207 // with b.N=1 to find any sub-benchmarks matching Y, which are 3208 // then run in full. 3209 // 3210 // -benchtime t 3211 // Run enough iterations of each benchmark to take t, specified 3212 // as a time.Duration (for example, -benchtime 1h30s). 3213 // The default is 1 second (1s). 3214 // The special syntax Nx means to run the benchmark N times 3215 // (for example, -benchtime 100x). 3216 // 3217 // -count n 3218 // Run each test, benchmark, and fuzz seed n times (default 1). 3219 // If -cpu is set, run n times for each GOMAXPROCS value. 3220 // Examples are always run once. -count does not apply to 3221 // fuzz tests matched by -fuzz. 3222 // 3223 // -cover 3224 // Enable coverage analysis. 3225 // Note that because coverage works by annotating the source 3226 // code before compilation, compilation and test failures with 3227 // coverage enabled may report line numbers that don't correspond 3228 // to the original sources. 3229 // 3230 // -covermode set,count,atomic 3231 // Set the mode for coverage analysis for the package[s] 3232 // being tested. The default is "set" unless -race is enabled, 3233 // in which case it is "atomic". 3234 // The values: 3235 // set: bool: does this statement run? 3236 // count: int: how many times does this statement run? 3237 // atomic: int: count, but correct in multithreaded tests; 3238 // significantly more expensive. 3239 // Sets -cover. 3240 // 3241 // -coverpkg pattern1,pattern2,pattern3 3242 // Apply coverage analysis in each test to packages whose import paths 3243 // match the patterns. The default is for each test to analyze only 3244 // the package being tested. See 'go help packages' for a description 3245 // of package patterns. Sets -cover. 3246 // 3247 // -cpu 1,2,4 3248 // Specify a list of GOMAXPROCS values for which the tests, benchmarks or 3249 // fuzz tests should be executed. The default is the current value 3250 // of GOMAXPROCS. -cpu does not apply to fuzz tests matched by -fuzz. 3251 // 3252 // -failfast 3253 // Do not start new tests after the first test failure. 3254 // 3255 // -fullpath 3256 // Show full file names in the error messages. 3257 // 3258 // -fuzz regexp 3259 // Run the fuzz test matching the regular expression. When specified, 3260 // the command line argument must match exactly one package within the 3261 // main module, and regexp must match exactly one fuzz test within 3262 // that package. Fuzzing will occur after tests, benchmarks, seed corpora 3263 // of other fuzz tests, and examples have completed. See the Fuzzing 3264 // section of the testing package documentation for details. 3265 // 3266 // -fuzztime t 3267 // Run enough iterations of the fuzz target during fuzzing to take t, 3268 // specified as a time.Duration (for example, -fuzztime 1h30s). 3269 // The default is to run forever. 3270 // The special syntax Nx means to run the fuzz target N times 3271 // (for example, -fuzztime 1000x). 3272 // 3273 // -fuzzminimizetime t 3274 // Run enough iterations of the fuzz target during each minimization 3275 // attempt to take t, as specified as a time.Duration (for example, 3276 // -fuzzminimizetime 30s). 3277 // The default is 60s. 3278 // The special syntax Nx means to run the fuzz target N times 3279 // (for example, -fuzzminimizetime 100x). 3280 // 3281 // -json 3282 // Log verbose output and test results in JSON. This presents the 3283 // same information as the -v flag in a machine-readable format. 3284 // 3285 // -list regexp 3286 // List tests, benchmarks, fuzz tests, or examples matching the regular 3287 // expression. No tests, benchmarks, fuzz tests, or examples will be run. 3288 // This will only list top-level tests. No subtest or subbenchmarks will be 3289 // shown. 3290 // 3291 // -parallel n 3292 // Allow parallel execution of test functions that call t.Parallel, and 3293 // fuzz targets that call t.Parallel when running the seed corpus. 3294 // The value of this flag is the maximum number of tests to run 3295 // simultaneously. 3296 // While fuzzing, the value of this flag is the maximum number of 3297 // subprocesses that may call the fuzz function simultaneously, regardless of 3298 // whether T.Parallel is called. 3299 // By default, -parallel is set to the value of GOMAXPROCS. 3300 // Setting -parallel to values higher than GOMAXPROCS may cause degraded 3301 // performance due to CPU contention, especially when fuzzing. 3302 // Note that -parallel only applies within a single test binary. 3303 // The 'go test' command may run tests for different packages 3304 // in parallel as well, according to the setting of the -p flag 3305 // (see 'go help build'). 3306 // 3307 // -run regexp 3308 // Run only those tests, examples, and fuzz tests matching the regular 3309 // expression. For tests, the regular expression is split by unbracketed 3310 // slash (/) characters into a sequence of regular expressions, and each 3311 // part of a test's identifier must match the corresponding element in 3312 // the sequence, if any. Note that possible parents of matches are 3313 // run too, so that -run=X/Y matches and runs and reports the result 3314 // of all tests matching X, even those without sub-tests matching Y, 3315 // because it must run them to look for those sub-tests. 3316 // See also -skip. 3317 // 3318 // -short 3319 // Tell long-running tests to shorten their run time. 3320 // It is off by default but set during all.bash so that installing 3321 // the Go tree can run a sanity check but not spend time running 3322 // exhaustive tests. 3323 // 3324 // -shuffle off,on,N 3325 // Randomize the execution order of tests and benchmarks. 3326 // It is off by default. If -shuffle is set to on, then it will seed 3327 // the randomizer using the system clock. If -shuffle is set to an 3328 // integer N, then N will be used as the seed value. In both cases, 3329 // the seed will be reported for reproducibility. 3330 // 3331 // -skip regexp 3332 // Run only those tests, examples, fuzz tests, and benchmarks that 3333 // do not match the regular expression. Like for -run and -bench, 3334 // for tests and benchmarks, the regular expression is split by unbracketed 3335 // slash (/) characters into a sequence of regular expressions, and each 3336 // part of a test's identifier must match the corresponding element in 3337 // the sequence, if any. 3338 // 3339 // -timeout d 3340 // If a test binary runs longer than duration d, panic. 3341 // If d is 0, the timeout is disabled. 3342 // The default is 10 minutes (10m). 3343 // 3344 // -v 3345 // Verbose output: log all tests as they are run. Also print all 3346 // text from Log and Logf calls even if the test succeeds. 3347 // 3348 // -vet list 3349 // Configure the invocation of "go vet" during "go test" 3350 // to use the comma-separated list of vet checks. 3351 // If list is empty, "go test" runs "go vet" with a curated list of 3352 // checks believed to be always worth addressing. 3353 // If list is "off", "go test" does not run "go vet" at all. 3354 // 3355 // The following flags are also recognized by 'go test' and can be used to 3356 // profile the tests during execution: 3357 // 3358 // -benchmem 3359 // Print memory allocation statistics for benchmarks. 3360 // Allocations made in C or using C.malloc are not counted. 3361 // 3362 // -blockprofile block.out 3363 // Write a goroutine blocking profile to the specified file 3364 // when all tests are complete. 3365 // Writes test binary as -c would. 3366 // 3367 // -blockprofilerate n 3368 // Control the detail provided in goroutine blocking profiles by 3369 // calling runtime.SetBlockProfileRate with n. 3370 // See 'go doc runtime.SetBlockProfileRate'. 3371 // The profiler aims to sample, on average, one blocking event every 3372 // n nanoseconds the program spends blocked. By default, 3373 // if -test.blockprofile is set without this flag, all blocking events 3374 // are recorded, equivalent to -test.blockprofilerate=1. 3375 // 3376 // -coverprofile cover.out 3377 // Write a coverage profile to the file after all tests have passed. 3378 // Sets -cover. 3379 // 3380 // -cpuprofile cpu.out 3381 // Write a CPU profile to the specified file before exiting. 3382 // Writes test binary as -c would. 3383 // 3384 // -memprofile mem.out 3385 // Write an allocation profile to the file after all tests have passed. 3386 // Writes test binary as -c would. 3387 // 3388 // -memprofilerate n 3389 // Enable more precise (and expensive) memory allocation profiles by 3390 // setting runtime.MemProfileRate. See 'go doc runtime.MemProfileRate'. 3391 // To profile all memory allocations, use -test.memprofilerate=1. 3392 // 3393 // -mutexprofile mutex.out 3394 // Write a mutex contention profile to the specified file 3395 // when all tests are complete. 3396 // Writes test binary as -c would. 3397 // 3398 // -mutexprofilefraction n 3399 // Sample 1 in n stack traces of goroutines holding a 3400 // contended mutex. 3401 // 3402 // -outputdir directory 3403 // Place output files from profiling in the specified directory, 3404 // by default the directory in which "go test" is running. 3405 // 3406 // -trace trace.out 3407 // Write an execution trace to the specified file before exiting. 3408 // 3409 // Each of these flags is also recognized with an optional 'test.' prefix, 3410 // as in -test.v. When invoking the generated test binary (the result of 3411 // 'go test -c') directly, however, the prefix is mandatory. 3412 // 3413 // The 'go test' command rewrites or removes recognized flags, 3414 // as appropriate, both before and after the optional package list, 3415 // before invoking the test binary. 3416 // 3417 // For instance, the command 3418 // 3419 // go test -v -myflag testdata -cpuprofile=prof.out -x 3420 // 3421 // will compile the test binary and then run it as 3422 // 3423 // pkg.test -test.v -myflag testdata -test.cpuprofile=prof.out 3424 // 3425 // (The -x flag is removed because it applies only to the go command's 3426 // execution, not to the test itself.) 3427 // 3428 // The test flags that generate profiles (other than for coverage) also 3429 // leave the test binary in pkg.test for use when analyzing the profiles. 3430 // 3431 // When 'go test' runs a test binary, it does so from within the 3432 // corresponding package's source code directory. Depending on the test, 3433 // it may be necessary to do the same when invoking a generated test 3434 // binary directly. Because that directory may be located within the 3435 // module cache, which may be read-only and is verified by checksums, the 3436 // test must not write to it or any other directory within the module 3437 // unless explicitly requested by the user (such as with the -fuzz flag, 3438 // which writes failures to testdata/fuzz). 3439 // 3440 // The command-line package list, if present, must appear before any 3441 // flag not known to the go test command. Continuing the example above, 3442 // the package list would have to appear before -myflag, but could appear 3443 // on either side of -v. 3444 // 3445 // When 'go test' runs in package list mode, 'go test' caches successful 3446 // package test results to avoid unnecessary repeated running of tests. To 3447 // disable test caching, use any test flag or argument other than the 3448 // cacheable flags. The idiomatic way to disable test caching explicitly 3449 // is to use -count=1. 3450 // 3451 // To keep an argument for a test binary from being interpreted as a 3452 // known flag or a package name, use -args (see 'go help test') which 3453 // passes the remainder of the command line through to the test binary 3454 // uninterpreted and unaltered. 3455 // 3456 // For instance, the command 3457 // 3458 // go test -v -args -x -v 3459 // 3460 // will compile the test binary and then run it as 3461 // 3462 // pkg.test -test.v -x -v 3463 // 3464 // Similarly, 3465 // 3466 // go test -args math 3467 // 3468 // will compile the test binary and then run it as 3469 // 3470 // pkg.test math 3471 // 3472 // In the first example, the -x and the second -v are passed through to the 3473 // test binary unchanged and with no effect on the go command itself. 3474 // In the second example, the argument math is passed through to the test 3475 // binary, instead of being interpreted as the package list. 3476 // 3477 // # Testing functions 3478 // 3479 // The 'go test' command expects to find test, benchmark, and example functions 3480 // in the "*_test.go" files corresponding to the package under test. 3481 // 3482 // A test function is one named TestXxx (where Xxx does not start with a 3483 // lower case letter) and should have the signature, 3484 // 3485 // func TestXxx(t *testing.T) { ... } 3486 // 3487 // A benchmark function is one named BenchmarkXxx and should have the signature, 3488 // 3489 // func BenchmarkXxx(b *testing.B) { ... } 3490 // 3491 // A fuzz test is one named FuzzXxx and should have the signature, 3492 // 3493 // func FuzzXxx(f *testing.F) { ... } 3494 // 3495 // An example function is similar to a test function but, instead of using 3496 // *testing.T to report success or failure, prints output to os.Stdout. 3497 // If the last comment in the function starts with "Output:" then the output 3498 // is compared exactly against the comment (see examples below). If the last 3499 // comment begins with "Unordered output:" then the output is compared to the 3500 // comment, however the order of the lines is ignored. An example with no such 3501 // comment is compiled but not executed. An example with no text after 3502 // "Output:" is compiled, executed, and expected to produce no output. 3503 // 3504 // Godoc displays the body of ExampleXxx to demonstrate the use 3505 // of the function, constant, or variable Xxx. An example of a method M with 3506 // receiver type T or *T is named ExampleT_M. There may be multiple examples 3507 // for a given function, constant, or variable, distinguished by a trailing _xxx, 3508 // where xxx is a suffix not beginning with an upper case letter. 3509 // 3510 // Here is an example of an example: 3511 // 3512 // func ExamplePrintln() { 3513 // Println("The output of\nthis example.") 3514 // // Output: The output of 3515 // // this example. 3516 // } 3517 // 3518 // Here is another example where the ordering of the output is ignored: 3519 // 3520 // func ExamplePerm() { 3521 // for _, value := range Perm(4) { 3522 // fmt.Println(value) 3523 // } 3524 // 3525 // // Unordered output: 4 3526 // // 2 3527 // // 1 3528 // // 3 3529 // // 0 3530 // } 3531 // 3532 // The entire test file is presented as the example when it contains a single 3533 // example function, at least one other function, type, variable, or constant 3534 // declaration, and no tests, benchmarks, or fuzz tests. 3535 // 3536 // See the documentation of the testing package for more information. 3537 // 3538 // # Controlling version control with GOVCS 3539 // 3540 // The 'go get' command can run version control commands like git 3541 // to download imported code. This functionality is critical to the decentralized 3542 // Go package ecosystem, in which code can be imported from any server, 3543 // but it is also a potential security problem, if a malicious server finds a 3544 // way to cause the invoked version control command to run unintended code. 3545 // 3546 // To balance the functionality and security concerns, the 'go get' command 3547 // by default will only use git and hg to download code from public servers. 3548 // But it will use any known version control system (bzr, fossil, git, hg, svn) 3549 // to download code from private servers, defined as those hosting packages 3550 // matching the GOPRIVATE variable (see 'go help private'). The rationale behind 3551 // allowing only Git and Mercurial is that these two systems have had the most 3552 // attention to issues of being run as clients of untrusted servers. In contrast, 3553 // Bazaar, Fossil, and Subversion have primarily been used in trusted, 3554 // authenticated environments and are not as well scrutinized as attack surfaces. 3555 // 3556 // The version control command restrictions only apply when using direct version 3557 // control access to download code. When downloading modules from a proxy, 3558 // 'go get' uses the proxy protocol instead, which is always permitted. 3559 // By default, the 'go get' command uses the Go module mirror (proxy.golang.org) 3560 // for public packages and only falls back to version control for private 3561 // packages or when the mirror refuses to serve a public package (typically for 3562 // legal reasons). Therefore, clients can still access public code served from 3563 // Bazaar, Fossil, or Subversion repositories by default, because those downloads 3564 // use the Go module mirror, which takes on the security risk of running the 3565 // version control commands using a custom sandbox. 3566 // 3567 // The GOVCS variable can be used to change the allowed version control systems 3568 // for specific packages (identified by a module or import path). 3569 // The GOVCS variable applies when building package in both module-aware mode 3570 // and GOPATH mode. When using modules, the patterns match against the module path. 3571 // When using GOPATH, the patterns match against the import path corresponding to 3572 // the root of the version control repository. 3573 // 3574 // The general form of the GOVCS setting is a comma-separated list of 3575 // pattern:vcslist rules. The pattern is a glob pattern that must match 3576 // one or more leading elements of the module or import path. The vcslist 3577 // is a pipe-separated list of allowed version control commands, or "all" 3578 // to allow use of any known command, or "off" to disallow all commands. 3579 // Note that if a module matches a pattern with vcslist "off", it may still be 3580 // downloaded if the origin server uses the "mod" scheme, which instructs the 3581 // go command to download the module using the GOPROXY protocol. 3582 // The earliest matching pattern in the list applies, even if later patterns 3583 // might also match. 3584 // 3585 // For example, consider: 3586 // 3587 // GOVCS=github.com:git,evil.com:off,*:git|hg 3588 // 3589 // With this setting, code with a module or import path beginning with 3590 // github.com/ can only use git; paths on evil.com cannot use any version 3591 // control command, and all other paths (* matches everything) can use 3592 // only git or hg. 3593 // 3594 // The special patterns "public" and "private" match public and private 3595 // module or import paths. A path is private if it matches the GOPRIVATE 3596 // variable; otherwise it is public. 3597 // 3598 // If no rules in the GOVCS variable match a particular module or import path, 3599 // the 'go get' command applies its default rule, which can now be summarized 3600 // in GOVCS notation as 'public:git|hg,private:all'. 3601 // 3602 // To allow unfettered use of any version control system for any package, use: 3603 // 3604 // GOVCS=*:all 3605 // 3606 // To disable all use of version control, use: 3607 // 3608 // GOVCS=*:off 3609 // 3610 // The 'go env -w' command (see 'go help env') can be used to set the GOVCS 3611 // variable for future go command invocations. 3612 package main 3613