How Does `go run` Differ From `go build` and `go install`?

Go: The Nuances of go run

The go run command is often used as a convenient way to execute Go code, but it differs significantly from go build and go install in its underlying function. Go build compiles the code into binary artifacts, while go install not only compiles but also installs the binaries to the system path.

How does go run work?

Unlike go build and go install, go run doesn't create a standalone binary file. Instead, it functions as a two-step process:

1. Compilation: go run first compiles the specified Go file into a temporary binary. This binary is stored in a temporary directory.
2. Execution: Once compilation is complete, go run immediately executes the temporary binary.

Therefore, go run essentially combines the compilation and execution steps into a single operation. This makes it a handy tool for quickly testing or experimenting with Go code, as it eliminates the need to manually compile the code using go build and then execute the resulting binary.

Additional Notes:

• The temporary binary is executed in the same process as go run itself.
• The temporary binary is deleted after execution, leaving no artifacts behind.
• go run cannot be used to compile packages or dependencies; it only executes the specified file.

The above is the detailed content of How Does `go run` Differ From `go build` and `go install`?. For more information, please follow other related articles on the PHP Chinese website!