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