Stop debugging Rust with print statements @letsgetrusty
Stop debugging Rust with print statements  @letsgetrusty
Uploaded October 2026 | Updated November 2026, 1 day ago
👉Join the Rust Live Accelerator waitlist: letsgetrusty.com/join/wv-r9DAvRvHWwI

Adding println! can make a Rust concurrency bug seem to disappear. We use an async ticket counter to show how stdout locking changes timing and hides a lost-update race. Then we switch to tracing with a non-blocking writer, use Shuttle to find and replay a failing schedule, and fix the counter with fetch_add.

Chapters
0:00 A race condition that println! can hide
2:26 How stdout locking changes task timing
3:10 Logging with a non-blocking tracing writer
3:58 Finding and replaying failing schedules with Shuttle
Stop debugging Rust with print statementsMicrosoft just gave up C/C++ (use Rust!)BLAZINGLY FAST Rust OptimizationsRusts Golden RuleThe ultimate Rust IDE is hereRust stole C++s best featuresRust YouTubers Tier ListA deep dive into Rust futuresHow Rust made Python 100x fasterRust 1.63.0Is it too late to become a software developer?When to Leak Memory in Rust
Lets Get Rusty |

Stop debugging Rust with print statements

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER