`exercise` package 3. exercise/ 폴더로 이동한 후, cargo run 커맨드로코드를 실행합니다: $ cd exercise $ cargo run Compiling exercise v0.1.0 (/home/mgeisler/tmp/exercise) Finished dev [unoptimized + debuginfo] target(s) in 에 작성합니다 fn main() { println!("수정해 주세요!"); } 5. cargo run 커맨드로 소스를 빌드하고 실행합니다: $ cargo run Compiling exercise v0.1.0 (/home/mgeisler/tmp/exercise) Finished dev [unoptimized + debuginfo] target(s) in

`exercise` package 3. exercise/ 폴더로 이동한 후, cargo run 커맨드로코드를 실행합니다: $ cd exercise $ cargo run Compiling exercise v0.1.0 (/home/mgeisler/tmp/exercise) Finished dev [unoptimized + debuginfo] target(s) in 에 작성합니다 fn main() { println!("수정해 주세요!"); } 5. cargo run 커맨드로 소스를 빌드하고 실행합니다: $ cargo run Compiling exercise v0.1.0 (/home/mgeisler/tmp/exercise) Finished dev [unoptimized + debuginfo] target(s) in

guided optimization Profile guided optimization is something else though. It is a special way of compiling and linking, that the compiler and linker use profiling information to know how best to optimize It makes debugging and testing new code in the application itself difficult. What is more, just compiling and running the entire application to check a one-line change in a small class is very time-consuming