# Field access in a Rust debug REPL, without reflection

**URL:** <https://users.rust-lang.org/t/field-access-in-a-rust-debug-repl-without-reflection/143139>\
**Category:** community\
**Created:** [October 19, 2026, 5:48am UTC](https://users.rust-lang.org/t/field-access-in-a-rust-debug-repl-without-reflection/143139 "2026-10-19T05:48:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yohei.senju](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/yohei.senju/32/54412_2.png) [@yohei.senju](https://users.rust-lang.org/u/yohei.senju)\
**Post date:** [October 19, 2026, 5:48am UTC](https://users.rust-lang.org/t/field-access-in-a-rust-debug-repl-without-reflection/143139/1 "2026-10-19T05:48:32Z")

</div>

One paragraph on the Ruby binding.pry experience: one line of code, no debugger setup, a live REPL at the breakpoint.  
The pain in Rust today: dbg! is one-way, lldb/gdb setup is heavy, so everyone falls back to println! debugging.

![669483167-537bdbad-8f46-49e7-ae1e-477f822f9c95](https://us1.discourse-cdn.com/flex019/uploads/rust_lang/original/3X/5/9/59cc6441797533dfba2279496208b5070c5b1dc4.gif)

For that reason, I implemented a crate that lets you experience Ruby's `binding.pry` in Rust as well.  
Please check here for details.: [GitHub - 100010/pry-rs: Ruby's binding.pry for Rust — drop pry!() in your code to pause execution and inspect variables in an interactive REPL ✒️ · GitHub](https://github.com/100010/pry-rs)