Go compilation and execution flow - Mini Project: Build & Apply

Go compilation and execution flow

📖 Scenario: You are learning how Go programs are compiled and executed. This project will guide you through creating a simple Go program, setting up a configuration variable, writing the main logic, and finally running the program to see the output.

🎯 Goal: Build a simple Go program that prints a greeting message using a variable and a function, demonstrating the compilation and execution flow in Go.

📋 What You'll Learn

Create a string variable with a greeting message

Create a boolean variable to control if the greeting should be printed

Write a function that returns the greeting message if the boolean is true

Print the result of the function call

💡 Why This Matters

🌍 Real World

Understanding how Go compiles and runs programs helps you write efficient and correct applications, from simple scripts to large servers.

💼 Career

Many software jobs require knowledge of Go's build and execution process to debug, optimize, and deploy Go applications effectively.

1

DATA SETUP: Create a greeting message variable

Create a string variable called greeting and set it to "Hello, Go learner!".

Go

package main

import "fmt"

// Your code here

Hint

Use var greeting string = "Hello, Go learner!" to declare the variable.

2

CONFIGURATION: Add a boolean control variable

Create a boolean variable called shouldPrint and set it to true.

Go

package main

import "fmt"

var greeting string = "Hello, Go learner!"

// Your code here

Hint

Use var shouldPrint bool = true to declare the boolean variable.

3

CORE LOGIC: Write a function to return the greeting

Write a function called getGreeting that returns a string. Inside the function, use an if statement to return greeting if shouldPrint is true, otherwise return an empty string "".

Go

package main

import "fmt"

var greeting string = "Hello, Go learner!"
var shouldPrint bool = true

// Your code here

Hint

Define func getGreeting() string and use if shouldPrint { return greeting } else return empty string.

4

OUTPUT: Print the greeting message

Write the main function and inside it, use fmt.Println to print the result of calling getGreeting().

Go

package main

import "fmt"

var greeting string = "Hello, Go learner!"
var shouldPrint bool = true

func getGreeting() string {
    if shouldPrint {
        return greeting
    }
    return ""
}

// Your code here

Hint

Define func main() and inside it call fmt.Println(getGreeting()).

Practice

1. What does the go build command do in Go programming?

easy

A. It compiles the code and creates an executable file.

B. It runs the code without compiling.

C. It only checks the code for errors without compiling.

D. It deletes the executable file.

Solution

1. Step 1: Understand the purpose of go build

   The go build command compiles Go source code into an executable binary file.

2. Step 2: Differentiate from other commands

   Unlike go run, go build does not run the program immediately but creates a file you can run later.

3. Final Answer:

   It compiles the code and creates an executable file. -> Option A

4. Quick Check:

   go build creates executable [OK]

Hint: Remember: build = compile and save executable [OK]

Common Mistakes:

• Confusing go build with go run
• Thinking go build runs the program immediately
• Believing go build only checks syntax

2. Which of the following is the correct way to compile and run a Go program in one step?

easy

A. go execute main.go

B. go build main.go

C. go run main.go

D. go compile main.go

Solution

1. Step 1: Identify the command that compiles and runs

   go run compiles the code and runs it immediately without creating an executable file.

2. Step 2: Check other options

   go build only compiles; go execute and go compile are not valid Go commands.

3. Final Answer:

   go run main.go -> Option C

4. Quick Check:

   go run compiles and runs [OK]

Hint: Use go run to compile and run instantly [OK]

Common Mistakes:

• Using go build to run directly
• Typing invalid commands like go execute
• Confusing compile-only and run commands

3. What will happen if you run the command go run main.go on a valid Go source file?

medium

A. It compiles the code, creates an executable file, and runs it.

B. It deletes the source file after running.

C. It only checks the code for errors but does not run it.

D. It compiles the code and runs it without creating an executable file.

Solution

1. Step 1: Understand go run behavior

   go run compiles the source code in memory and runs it immediately without saving an executable file.

2. Step 2: Eliminate incorrect options

   It compiles the code, creates an executable file, and runs it. is wrong because no executable file is saved. It only checks the code for errors but does not run it. is wrong because it runs the program. It deletes the source file after running. is incorrect as source files are never deleted.

3. Final Answer:

   It compiles the code and runs it without creating an executable file. -> Option D

4. Quick Check:

   go run compiles & runs, no file saved [OK]

Hint: Run with go run to skip saving executable [OK]

Common Mistakes:

• Assuming go run saves an executable
• Thinking go run only checks syntax
• Believing source files get deleted

4. You run go build on your Go program, but no executable file appears. What is the most likely reason?

medium

A. Go automatically deletes the executable after building.

B. The source file has syntax errors preventing compilation.

C. The executable is created but hidden in a different directory.

D. The go build command only runs the program, not build it.

Solution

1. Step 1: Understand go build behavior on errors

   If the source code has syntax errors, go build will fail and not create an executable file.

2. Step 2: Check other options

   go build does not run the program, executables are created in the current directory by default, and Go does not delete executables automatically.

3. Final Answer:

   The source file has syntax errors preventing compilation. -> Option B

4. Quick Check:

   Syntax errors block build, no executable made [OK]

Hint: Check for syntax errors if no executable appears [OK]

Common Mistakes:

• Expecting go build to run the program
• Looking in wrong directories without checking errors
• Assuming Go deletes executables automatically

5. You want to quickly test a small Go program without creating an executable file. Which command should you use and why?

hard

A. Use go run because it compiles and runs the program without saving an executable.

B. Use go build because it compiles and runs the program immediately.

C. Use go install because it runs the program without compiling.

D. Use go test because it compiles and runs the program.

Solution

1. Step 1: Identify the command for quick testing

   go run compiles and runs the program immediately without creating an executable file, perfect for quick tests.

2. Step 2: Understand why other commands don't fit

   go build creates an executable but does not run it. go install compiles and installs packages, not for quick runs. go test runs tests, not general programs.

3. Final Answer:

   Use go run because it compiles and runs the program without saving an executable. -> Option A

4. Quick Check:

   Quick test = go run [OK]

Hint: Use go run for quick compile-and-run tests [OK]

Common Mistakes:

• Using go build expecting immediate run
• Confusing go install with running code
• Trying go test for normal program execution