liveBook · Manning

Compile time

Compile time is the phase before program execution when source code is analyzed, transformed, or translated and compile-time properties are determined.

How 2 Manning books explain it

Write Powerful Rust Macros

Compile time is the phase in which source code is analyzed and transformed into an executable or library artifact.

How it is used
Positions compile time as the stage where Rust macros generate ordinary code before linting, type checking, and artifact production.
How deep it goes
Traces macro expansion through later build stages but does not detail compiler internals or expansion implementation.
Examples
Uses macro-generated structs and functions, a hidden-code figure, and a blanket implementation for Copy types.
What you can do after
Evaluate compile-time cost and choose macros only when their boilerplate reduction outweighs understandability and build-time trade-offs.

Read how Write Powerful Rust Macros explains compile time →

Learn Rust in a Month of Lunches

Compile time is the phase before program execution in which source code is analyzed and transformed into executable code.

How it is used
Frames compile time as the programmer’s window for finding problems before program execution.
How deep it goes
Explains the compile-time/runtime boundary and walks through compiler corrections, but defers detailed language rules.
Examples
Uses Rust Playground code involving String conversion, character pushing, formatting punctuation, mutability, and an unused variable.
What you can do after
Diagnose compiler feedback and apply suggested corrections before running a Rust program.

Read how Learn Rust in a Month of Lunches explains compile time →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.