Bird
Raised Fist0
Rustprogramming~5 mins

Compilation and execution flow in Rust

Choose your learning style10 modes available
Introduction

Compilation and execution flow shows how Rust code turns into a running program. It helps you understand what happens behind the scenes.

When you want to know how Rust code becomes an executable file.
When you want to debug why your Rust program does not run as expected.
When you want to optimize your Rust code by understanding compilation steps.
When you are learning Rust and want to see how source code turns into output.
When you want to explain Rust program behavior to others.
Syntax
Rust
1. Write Rust source code in a .rs file
2. Use 'rustc filename.rs' to compile the code
3. The compiler creates an executable file
4. Run the executable to see the program output

The Rust compiler is called rustc.

Compilation checks your code for errors before creating the executable.

Examples
This command compiles the Rust file main.rs into an executable.
Rust
rustc main.rs
This runs the compiled executable named main on Unix-like systems.
Rust
./main
This runs the compiled executable on Windows systems.
Rust
main.exe
Sample Program

This simple Rust program prints a greeting. You compile it with rustc and then run the executable to see the message.

Rust
fn main() {
    println!("Hello, Rust!");
}
OutputSuccess
Important Notes

Compilation stops if there are errors in your code.

The executable file name depends on your source file name and operating system.

You can use cargo for bigger projects to manage compilation and execution easily.

Summary

Rust code is first compiled by rustc into an executable file.

Then you run the executable to see the program's output.

This flow helps catch errors early and creates fast programs.

Practice

(1/5)
1. What is the first step when running a Rust program?
easy
A. Directly run the Rust source file without compiling
B. Compile the code using rustc to create an executable
C. Write the output to a file before compiling
D. Use an interpreter to execute the Rust code line by line

Solution

  1. Step 1: Understand Rust's execution model

    Rust is a compiled language, so the source code must be compiled first.
  2. Step 2: Identify the compilation tool

    The rustc compiler converts Rust code into an executable file.
  3. Final Answer:

    Compile the code using rustc to create an executable -> Option B
  4. Quick Check:

    Rust code is compiled first [OK]
Hint: Rust code must be compiled before running [OK]
Common Mistakes:
  • Thinking Rust runs like a script without compiling
  • Confusing Rust with interpreted languages
  • Trying to run source code directly
2. Which command correctly compiles a Rust file named main.rs?
easy
A. run rustc main.rs
B. compile main.rs
C. rustc main.rs
D. cargo run main.rs

Solution

  1. Step 1: Recall Rust compilation command

    The Rust compiler command is rustc followed by the filename.
  2. Step 2: Check each option

    rustc main.rs matches the correct syntax: rustc main.rs.
  3. Final Answer:

    rustc main.rs -> Option C
  4. Quick Check:

    Use rustc filename.rs to compile [OK]
Hint: Use 'rustc' followed by filename to compile [OK]
Common Mistakes:
  • Adding extra words like 'run' before rustc
  • Using 'compile' instead of 'rustc'
  • Confusing cargo commands with rustc
3. What will be the output when running this Rust program?
fn main() {
    println!("Hello, Rust!");
}
medium
A. Hello, Rust!
B. println!("Hello, Rust!");
C. Error: missing semicolon
D. No output

Solution

  1. Step 1: Understand the println! macro

    This macro prints the string inside quotes to the console with a newline.
  2. Step 2: Check the code correctness

    The code is syntactically correct and will print the message.
  3. Final Answer:

    Hello, Rust! -> Option A
  4. Quick Check:

    println! outputs the string [OK]
Hint: println! prints text to console with newline [OK]
Common Mistakes:
  • Thinking println! prints the code itself
  • Expecting no output without return statement
  • Confusing macro syntax with function
4. Identify the error in this Rust code snippet:
fn main() {
    println!("Hello, world!")
}
medium
A. Missing closing parenthesis for println! macro
B. No error, code runs fine
C. Incorrect function name
D. Missing semicolon after println! macro

Solution

  1. Step 1: Check statement termination syntax

    Rust requires semicolons to terminate expression statements like println! macro calls.
  2. Step 2: Locate the missing semicolon

    The println! call is missing the terminating semicolon before the closing brace.
  3. Final Answer:

    Missing semicolon after println! macro -> Option D
  4. Quick Check:

    Expression statements require semicolon [OK]
Hint: Rust expression statements require a trailing semicolon [OK]
Common Mistakes:
  • Thinking it's a parenthesis mismatch
  • Confusing macros with block expressions
  • Believing no semicolon needed before closing brace
5. You have two Rust files: lib.rs and main.rs. You want to compile main.rs which uses functions from lib.rs. What is the correct compilation and execution flow?
hard
A. Compile lib.rs into a library, then compile main.rs linking the library, then run the executable
B. Run main.rs directly without compiling lib.rs
C. Compile only main.rs, Rust automatically compiles lib.rs
D. Combine both files manually into one file before compiling

Solution

  1. Step 1: Understand Rust's multi-file compilation

    The rustc compiler automatically handles referenced modules like lib.rs when compiling main.rs.
  2. Step 2: Single command suffices

    With mod lib; in main.rs, rustc main.rs compiles both files and produces the executable.
  3. Final Answer:

    Compile lib.rs into a library, then compile main.rs linking the library, then run the executable -> Option A
  4. Quick Check:

    rustc main.rs compiles dependencies automatically [OK]
Hint: rustc compiles referenced modules automatically [OK]
Common Mistakes:
  • Trying to run source files without compiling dependencies
  • Assuming Rust compiles dependencies automatically at runtime
  • Manually merging files instead of compiling separately
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard