LOADING
This talk explains how Rust debugging actually works: how compiler-generated debuginfo (DWARF/PDB) maps binaries back to source, and how LLDB/GDB interpret that data in practice.
Debugging Rust can feel opaque when traditional C/C++ debuggers misread enums, traits, and other Rust features. This talk explains how Rust debugging actually works: how compiler-generated debuginfo (DWARF/PDB) maps binaries back to source, and how LLDB/GDB interpret that data in practice. We’ll compare vanilla setups with Rust-specific extensions like pretty-printers, showing why they’re essential for inspecting Option, Result, and collections accurately. You’ll learn the real limits of expression evaluation (including why Debug/Display impls aren’t usable in-session yet) and what emerging techniques, such as compiling expressions to MIR (mid-level intermediate representation), promise for the future. We’ll finish with a practical troubleshooting checklist for breakpoints that don’t hit, variables that “disappear,” mysterious garbage values, and sluggish sessions. Whether you mostly rely on println! or regularly step through threads and stack frames, you’ll leave with a clearer mental model and concrete tactics to make interactive debugging a daily tool, not a last resort.
This talk explores building a complete self-hosted LLM stack in Rust: Paddler, a distributed load balancer for serving LLMs at scale, and Poet, a static site generator that consumes those LLMs for AI-powered content features.
In this introductory talk, we will explore what it means to "Ratatuify" the Rust package manager, Cargo.
In this talk, we’ll explore battle-tested best practices for integrating Claude Code into a professional Axum development workflow without compromising on Rust’s core values: correctness, clarity, and maintainability.
In 2024, I added the `Option::as_slice` and `Option::as_mut_slice` methods to libcore. This talk is about what motivated the addition, and looks into the no less than 4 different implementations that made up the methods. It also shows that even without a deep understanding of all compiler internals, it is possible to add changes both to the compiler and standard library.
During this talk we'll build a basic, working async runtime using nothing more than a standard library. The point? To see it's approachable for mere mortals.
